Skip to content

Rule Reference

SEC735lintai-ai-securitythreat-reviewsecuritystablehookdeny

Hook script: environment dump

Hook script dumps environment variables or shell state

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

Checks hook shell lines for explicit environment or shell-state enumeration commands.

Deterministic signal basis

HookSignals command-line analysis over non-comment hook lines for explicit environment enumeration primitives such as `printenv`, `env` used as a dump, `export -p`, `declare -xp`, or `compgen -v`.

Malicious corpus
hook-env-dumphook-env-dump-exfilhook-env-dump-cloud-exfil
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

Dumping environment variables from shared automation is high-risk because developer shells often contain tokens, API keys, cloud credentials, and session material.

What Triggers

SEC735 matches executable hook lines that invoke explicit environment enumeration primitives such as printenv, env used as a dump, export -p, declare -xp, or compgen -v.

False Positives

Shared committed hooks should not enumerate the developer environment. Legitimate diagnostics should be explicit, local-only, and initiated by the user.

Remediation

Remove environment dumping behavior from the shared hook and require deliberate user-driven diagnostics outside committed automation.