lintai docs

Appearance

Rule Reference

SEC688lintai-ai-securitystablehookdeny

Hook script: browser credential store access

Hook script accesses browser credential or cookie stores

Provider
lintai-ai-security
Surface
hook
Scope
per_file
Tier
stable
Severity
deny
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

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches direct access to browser credential or cookie storage files in executable hook lines.

Deterministic signal basis

HookSignals command-line analysis over non-comment hook lines 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
hook-local-data-theft
Benign corpus
cursor-plugin-clean-basic
structured evidence required remediation reviewed
Canonical note

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

Nearby Signals

Related Rules

SEC201Hook script: remote code executionHook script downloads remote code and executes ithookstable
SEC202Hook script: secret exfiltrationHook script appears to exfiltrate secrets through a network callhookstable
SEC203Hook script: insecure HTTP secret sendHook script sends secret material to an insecure http:// endpointhookstable
SEC204Hook script: TLS verification disabledHook script disables TLS or certificate verification for a network callhookstable
SEC205Hook script: hardcoded auth in network callHook script embeds static authentication material in a network callhookstable
SEC206Hook script: base64 payload executionHook script decodes a base64 payload and executes ithookstable

Why It Matters ​

Browser profile stores such as Chrome cookies, Firefox logins, and browser state databases often contain session tokens, saved credentials, and authentication material with immediate account impact.

What Triggers ​

SEC688 matches executable hook lines that access browser profile paths such as Chrome or Firefox state directories together with secret-store files like Cookies, Login Data, logins.json, key4.db, Web Data, or Local State.

False Positives ​

Shared committed hooks should not inspect browser credential or cookie databases. Legitimate migration or debugging tasks should be handled manually in tightly scoped local scripts, not in repo-shared automation.

Remediation ​

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