Skip to content

Rule Reference

SEC709lintai-ai-securitythreat-reviewsecuritystablejsonwarn

Plugin hook: screen capture

Plugin hook command captures a screenshot or desktop image

Public lane
threat-review
Category
security
Provider
lintai-ai-security
Scope
per-file
Surface
json
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 plugin hook command values for explicit screen capture utilities.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks for explicit screen capture utilities such as `screencapture`, `scrot`, `gnome-screenshot`, `grim`, `maim`, `grimshot`, ImageMagick `import -window root`, or PowerShell `CopyFromScreen`.

Malicious corpus
plugin-hook-command-screen-captureplugin-hook-command-screen-capture-exfil
Benign corpus
plugin-hook-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 plugin hooks execute in developer environments, so screenshot capture from them is strong evidence of spyware-like collection behavior.

What Triggers

SEC709 matches committed plugin hook command values 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 plugin hooks should not capture screenshots from developer machines. If a screen capture workflow is truly needed, it should be explicit and outside repo-shared automation.

Remediation

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