Skip to content

Rule Reference

SEC683lintai-ai-securitythreat-reviewsecuritystablehookdeny

Hook script: sensitive file exfiltration

Hook script transfers a sensitive credential file to a remote destination

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 transfer of sensitive credential files to remote network or cloud-storage destinations in executable hook lines.

Deterministic signal basis

HookSignals command-line analysis over non-comment hook lines for sensitive file paths such as `.env`, `.aws/credentials`, `.ssh/id_rsa`, or `.kube/config` combined with transfer commands like `scp`, `sftp`, `rsync`, `curl`, `aws s3 cp`, `gsutil cp`, or `rclone copy`.

Malicious corpus
hook-sensitive-file-exfilhook-sensitive-file-rclone-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

Shared hooks should not export local credential files such as SSH keys, cloud credentials, or .env files to remote systems or buckets.

What Triggers

SEC683 matches executable hook lines that pair sensitive file paths like .env, ~/.aws/credentials, ~/.ssh/id_rsa, or ~/.kube/config with transfer commands such as scp, rsync, curl --upload-file, aws s3 cp, or gsutil cp.

False Positives

Some setup scripts move local files between trusted systems, but committed shared hooks should not silently transfer credential-bearing files as part of normal execution.

Remediation

Remove the remote transfer of sensitive credential files from the hook and keep credential material local to the trusted system that owns it.