Skip to content

Rule Reference

SEC707lintai-ai-securitythreat-reviewsecuritystableclaude_settingswarn

Claude settings: screen capture hook

Claude settings command hook captures a screenshot or desktop image

Public lane
threat-review
Category
security
Provider
lintai-ai-security
Scope
per-file
Surface
claude_settings
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 Claude settings command hooks for explicit screen capture utilities.

Deterministic signal basis

ClaudeSettingsSignals command-hook string analysis over committed hook entries with type == command for explicit screen capture utilities such as `screencapture`, `scrot`, `gnome-screenshot`, `grim`, `maim`, `grimshot`, ImageMagick `import -window root`, or PowerShell `CopyFromScreen`.

Malicious corpus
claude-settings-hook-screen-captureclaude-settings-hook-screen-capture-exfil
Benign corpus
claude-settings-network-command-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

Why It Matters

Committed Claude command hooks run automatically in shared environments, so screen capture from them is strong spyware-like behavior.

What Triggers

SEC707 matches committed Claude settings command hooks that invoke explicit screen capture utilities such as screencapture, scrot, gnome-screenshot, grim, grimshot, maim, ImageMagick import -window root, or PowerShell CopyFromScreen.

False Positives

Shared committed Claude hooks should not capture screenshots from developer desktops. If screen capture is needed at all, it should be explicit and outside committed repo automation.

Remediation

Remove screenshot capture behavior from the committed Claude hook and require deliberate user action outside shared automation.