lintai docs

Appearance

Rule Reference

SEC694lintai-ai-securitystablejsonwarn

Plugin hook: browser credential store access

Plugin hook command accesses browser credential or cookie stores

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 direct access to browser credential or cookie storage files.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks for browser profile paths such as Chrome or Firefox state directories paired with secret-store files like `Cookies`, `Login Data`, `logins.json`, `key4.db`, `Web Data`, or `Local State`.

Malicious corpus
plugin-hook-command-local-data-theft
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 ​

Browser cookie and credential stores can contain live sessions and saved authentication data, so shared plugin hooks should never access them.

What Triggers ​

SEC694 matches committed plugin hook command values that access browser profile directories together with secret-store files like Cookies, Login Data, logins.json, key4.db, Web Data, or Local State.

False Positives ​

Committed plugin hooks should not inspect browser credential databases. Any legitimate local inspection should be kept outside repo-shared automation.

Remediation ​

Remove browser credential and cookie store access from the committed plugin hook and keep browser profile data outside committed automation.