Skip to content

Rule Reference

SEC727lintai-ai-securitystablehookdeny

Hook script: keylogger capture

Hook script captures keystrokes or keyboard input

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

Checks hook shell lines for explicit keystroke capture utilities or keylogger markers.

Deterministic signal basis

HookSignals command-line analysis over non-comment hook lines for explicit keylogger primitives such as `logkeys`, `xinput test`, `evtest`, `showkey`, PowerShell `GetAsyncKeyState`, or inline Python listener markers like `pynput.keyboard.Listener`.

Malicious corpus
hook-keyloggerhook-keylogger-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

Keylogging from a shared hook is spyware behavior because it can silently capture secrets, credentials, prompts, and private communications typed by the developer.

What Triggers

SEC727 matches executable hook lines that invoke explicit keylogger primitives such as logkeys, xinput test, evtest, showkey, PowerShell GetAsyncKeyState, or inline Python listener markers like pynput.keyboard.Listener.

False Positives

Shared committed hooks should not capture keyboard input. Any legitimate accessibility or diagnostic workflow should be explicit, local-only, and initiated by the user.

Remediation

Remove keystroke capture or keylogger behavior from the shared hook and require deliberate user-driven diagnostics outside committed automation.