lintai docs

Appearance

Rule Reference

SEC305lintai-ai-securitythreat-reviewsecuritystablejsonwarn

Config: hardcoded auth material

Configuration embeds static authentication material in a connection or auth value

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.

threat-reviewsidecar lane
mcpsurface preset

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Matches literal static auth material embedded directly in configuration values.

Deterministic signal basis

JsonSignals literal authorization or userinfo span extraction excluding dynamic placeholders.

Malicious corpus
mcp-static-authorization
Benign corpus
mcp-authorization-placeholder-safe
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

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cthreat-reviewsecurityjson
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesthreat-reviewsecurityjson
SEC310Config: metadata or private-network hostConfiguration endpoint targets a metadata or private-network host literalthreat-reviewsecurityjson
SEC338MCP config: sensitive host bind mountMCP configuration launches Docker with a bind mount of sensitive host materialthreat-reviewsecurityjson
SEC339MCP config: privileged Docker flagsMCP configuration launches Docker with a host-escape or privileged runtime flagthreat-reviewsecurityjson
SEC422MCP config: sudo commandMCP configuration launches the server through `sudo`threat-reviewsecurityjson

Why It Matters ​

Literal credentials embedded directly in config values turn the committed artifact itself into a secret carrier. That makes review, rotation, and downstream reuse materially harder.

What Triggers ​

SEC305 applies to parsed JSON config values and triggers when literal auth material appears in:

  • URL userinfo
  • authorization-like values
  • other direct auth fields

Examples that trigger:

json
{"endpoint":"https://deploy-token@internal.test/bootstrap"}
{"authorization":"Bearer static-token-value"}

Example that stays clean:

json
{"authorization":"Bearer ${SERVICE_TOKEN}"}

False Positives ​

The detector excludes dynamic placeholders and focuses on literal committed auth material. That keeps the rule in the structural stable lane rather than the heuristic preview bucket.

Remediation ​

Remove embedded credentials from config values and source auth from environment, secret stores, or provider-local configuration.