Skip to content

Rule Reference

SEC696lintai-ai-securitythreat-reviewsecuritystablehookdeny

Hook script: browser credential store exfiltration

Hook script exfiltrates browser credential or cookie store data

Public lane
threat-review
Category
security
Provider
lintai-ai-security
Scope
per-file
Surface
hook
Tier
stable
Severity
deny
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Explicit malicious, secret-bearing, or spyware-like review.

How to read this category

Strong exploit, secret, or unsafe-execution signal.

Activation Model

Preset Activation

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

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Matches direct access to browser credential or cookie storage files combined with remote transfer behavior 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`, combined with remote sinks such as `curl`, `wget`, `scp`, `rsync`, `nc`, or HTTP(S) endpoints.

Malicious corpus
hook-local-data-exfil
Benign corpus
cursor-plugin-clean-basic
structured evidence required remediation reviewed
Canonical note

Structural stable rule positioned as an explicit threat-review control: high-signal malicious, credential-bearing, or spyware-like behavior that stays opt-in rather than shaping the quiet default.

Nearby Signals

Related Rules

Why It Matters

Browser profile files such as cookies, saved logins, and browser state databases can contain live sessions and authentication material. Sending them off-host is high-confidence account theft behavior.

What Triggers

SEC696 matches executable hook lines that access browser profile paths together with secret-store files like Cookies, Login Data, logins.json, key4.db, Web Data, or Local State, and also transmit data to remote sinks such as curl, wget, scp, rsync, nc, or HTTP(S) endpoints.

False Positives

Shared committed hooks should not collect and transmit browser credential or cookie store data. Any local diagnostic or migration task that truly needs browser data should stay out of repo-shared automation.

Remediation

Remove network exfiltration of browser credential and cookie store data from the shared hook and keep browser profile data local.