Skip to content

Rule Reference

SEC703lintai-ai-securitystablehookdeny

Hook script: screen capture

Hook script captures a screenshot or desktop image

Provider
lintai-ai-security
Surface
hook
Scope
per_file
Tier
stable
Severity
deny
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Matches explicit screen capture utilities in executable hook lines.

Deterministic signal basis

HookSignals command-line analysis over non-comment hook lines for explicit screen capture utilities such as `screencapture`, `scrot`, `gnome-screenshot`, `grim`, `maim`, `grimshot`, ImageMagick `import -window root`, or PowerShell `CopyFromScreen`.

Malicious corpus
hook-screen-capturehook-screen-capture-exfil
Benign corpus
cursor-plugin-clean-basic
structured evidence required remediation reviewed
Canonical note

Structural stable rule intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

Why It Matters

Screen capture from a shared hook is spyware-like behavior because it can silently collect tokens, chats, dashboards, terminals, or other sensitive material visible on the developer's desktop.

What Triggers

SEC703 matches executable hook lines 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 hooks should not capture screenshots from developer machines. Any legitimate screenshot workflow should be explicit, local-only, and outside repo-shared automation.

Remediation

Remove screenshot capture behavior from the shared hook and require deliberate, user-driven capture outside committed automation.