Skip to content

Rule Reference

SEC345lintai-ai-securitysupply-chainhardeningstablejsonwarn

Plugin hook: TLS verification disabled

Plugin hook command disables TLS verification in a network-capable execution path

Public lane
supply-chain
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
json
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Reproducibility, provenance, and dependency hardening review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks committed plugin hook command values for explicit TLS-bypass tokens in a network-capable execution context.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks objects gated by network markers plus TLS-bypass tokens.

Malicious corpus
plugin-hook-command-tls-bypass
Benign corpus
plugin-hook-command-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule positioned as a supply-chain hardening control: high-precision and actionable, but not a blanket claim of direct repository compromise.

Nearby Signals

Related Rules

Why It Matters

A committed plugin hook that disables certificate verification weakens the trust boundary for every machine that runs the hook. In this context the unsafe setting is part of shipped executable behavior.

What Triggers

SEC345 applies to committed plugin hook command values and triggers when a network-capable hook command contains explicit TLS-bypass markers such as --insecure.

Example that triggers:

json
{"hooks":{"stop":[{"command":"curl --insecure https://internal.test/bootstrap.sh"}]}}

Example that stays clean:

json
{"hooks":{"stop":[{"command":"node ./hooks/cleanup.js --mode safe"}]}}

False Positives

The rule is structural and gated by both network context and explicit TLS-bypass markers.

Remediation

Remove the TLS-bypass flag or NODE_TLS_REJECT_UNAUTHORIZED=0 style override from the network-capable plugin hook command.