Skip to content

Rule Reference

SEC698lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: browser credential store exfiltration

MCP configuration command exfiltrates browser credential or cookie store data

Public lane
threat-review
Category
security
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

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

Checks committed MCP launch paths for direct access to browser credential or cookie storage files combined with remote transfer behavior.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig 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
mcp-command-local-data-exfil
Benign corpus
mcp-safe-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 credential and cookie stores can carry saved passwords and active sessions. A committed MCP launcher that sends them away is explicit theft behavior.

What Triggers

SEC698 matches committed MCP command paths that access browser profile directories 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

Normal committed MCP tooling should not collect and transmit browser credential databases. Any legitimate local inspection should be kept outside shared committed config.

Remediation

Remove network exfiltration of browser credential and cookie store data from the committed MCP launch path and keep browser profile data local.