lintai docs

Appearance

Rule Reference

SEC680lintai-ai-securitystablejsonwarn

Plugin hook: secret exfiltration

Plugin hook command appears to send secret material over the network

Provider
lintai-ai-security
Surface
json
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks committed plugin hook command values for explicit secret-bearing network exfil payloads.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks for secret markers combined with network-capable command context.

Malicious corpus
plugin-hook-command-secret-exfil-payloads
Benign corpus
plugin-hook-command-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationjsonstable
SEC305Config: hardcoded auth materialConfiguration embeds static authentication material in a connection or auth valuejsonstable
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesjsonstable

Why It Matters ​

Committed plugin hook commands run as part of the plugin lifecycle, so any secret-bearing network send becomes part of the default execution path for downstream users.

What Triggers ​

SEC680 matches plugin hook commands that combine secret markers with a network-capable command path.

False Positives ​

If a plugin needs authenticated access, keep secret handling inside the plugin logic or server process rather than in a raw shared hook command.

Remediation ​

Remove the secret-bearing network send from the committed plugin hook and keep secret access local to the trusted component.