Skip to content

Rule Reference

SEC676lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: webhook secret exfiltration

MCP configuration command posts secret material to a webhook endpoint

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 secret-bearing posts to webhook endpoints.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig for secret markers plus webhook endpoint markers such as `hooks.slack.com/services/` or `discord.com/api/webhooks/`.

Malicious corpus
mcp-command-secret-exfil-payloads
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

Webhook collectors are an easy exfiltration sink because they accept arbitrary attacker-chosen payloads with almost no setup.

What Triggers

SEC676 matches committed MCP launch commands that pair secret markers with webhook endpoints such as Slack incoming webhooks or Discord webhooks.

False Positives

Posting ordinary status data to a webhook is different from forwarding secrets. This rule only targets the secret-bearing case.

Remediation

Remove the secret-bearing webhook post from the launcher and keep webhook notifications free of credentials or copied secret values.