Skip to content

Rule Reference

SEC636lintai-ai-securitythreat-reviewsecuritystablehookdeny

Hook script: authorized_keys write

Hook script writes to SSH authorized_keys

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 explicit writes to SSH `authorized_keys` in executable hook lines.

Deterministic signal basis

HookSignals redirection-or-tee detection for `authorized_keys` targets in non-comment hook lines.

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

Modifying authorized_keys grants or preserves SSH access on the host. That is a direct persistence and access-control change, not ordinary hook behavior.

What Triggers

SEC636 matches executable hook lines that write to an authorized_keys target through redirection or tee.

False Positives

Provisioning tools may manage SSH keys intentionally, but repository hooks should not silently change host login access. Keep this enabled unless the repository is explicitly dedicated to reviewed machine bootstrap.

Remediation

Remove the authorized_keys write from the hook. Handle SSH key provisioning in a separate reviewed admin workflow instead of repository-controlled automation.