Skip to content

Rule Reference

SEC640lintai-ai-securitythreat-reviewsecuritystablejsonwarn

MCP config: authorized_keys write

MCP configuration command writes to SSH authorized_keys

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 explicit writes to SSH `authorized_keys`.

Deterministic signal basis

JsonSignals command-plus-args analysis over ArtifactKind::McpConfig using redirection-or-tee targeting of `authorized_keys`.

Malicious corpus
mcp-command-persistence-escalation
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

An MCP command that modifies authorized_keys can grant persistent SSH access to the host.

What Triggers

SEC640 matches MCP command definitions that write to an authorized_keys target, including redirection in a command string or structured tee invocations aimed at an authorized_keys path.

False Positives

Provisioning systems sometimes manage SSH keys intentionally, but shared MCP launch config should not silently change host login access.

Remediation

Remove the authorized_keys modification from the MCP config. Handle SSH key management in a dedicated reviewed provisioning path instead.