lintai docs

Appearance

Rule Reference

SEC660lintai-ai-securitystablejsonwarn

Plugin hook: launchd persistence

Plugin hook command registers a launchd plist for persistence

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

Activation Model

Preset Membership

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

basemembership
mcpmembership

Lifecycle

Stable Lifecycle Contract

State

stable_gated

Graduation rationale

Checks committed plugin hook command values for explicit launchd registration or LaunchAgents/LaunchDaemons plist writes.

Deterministic signal basis

JsonSignals command-string analysis over ArtifactKind::CursorPluginHooks for `launchctl load|bootstrap` or writes to LaunchAgents/LaunchDaemons plist paths.

Malicious corpus
plugin-hook-command-service-persistence
Benign corpus
plugin-hook-command-safe
structured evidence required remediation reviewed
Canonical note

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

Nearby Signals

Related Rules

SEC301MCP config: shell trampolineMCP configuration shells out through sh -c or bash -cjsonstable
SEC302Config: insecure HTTP endpointConfiguration contains an insecure http:// endpointjsonstable
SEC303MCP config: credential env passthroughMCP configuration passes through credential environment variablesjsonstable
SEC304Config: TLS verification disabledConfiguration disables TLS or certificate verificationjsonstable
SEC305Config: hardcoded auth materialConfiguration embeds static authentication material in a connection or auth valuejsonstable
SEC309Config: literal secrets in configConfiguration commits literal secret material in env, auth, or header valuesjsonstable

Why It Matters ​

Launchd registration from a plugin hook can install persistent macOS execution controlled by repository-delivered automation.

What Triggers ​

SEC660 matches plugin hook command strings that run launchctl load or launchctl bootstrap, or write plist files into LaunchAgents or LaunchDaemons paths.

False Positives ​

Bootstrap-style plugins may intentionally manage launchd, but silent host persistence is still risky and should be explicit.

Remediation ​

Remove launchd persistence from the plugin hook and keep plist registration in a separate reviewed administrative setup path.