Skip to content

Rule Reference

SEC650lintai-ai-securitythreat-reviewsecuritystablehookdeny

Hook script: systemd persistence

Hook script registers a systemd service or unit for persistence

Public lane
threat-review
Category
security
Provider
lintai-ai-security
Scope
per-file
Surface
hook
Tier
stable
Severity
deny
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

Matches explicit systemd service registration or unit-file writes in executable hook lines.

Deterministic signal basis

HookSignals command-or-write-target detection over non-comment hook lines for `systemctl enable|link` or writes to systemd unit paths.

Malicious corpus
hook-service-persistence
Benign corpus
cursor-plugin-clean-basic
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

Registering systemd units makes repository-delivered automation persist across boots or logins.

What Triggers

SEC650 matches executable hook lines that run systemctl enable or systemctl link, or write unit files into systemd service paths such as /etc/systemd/system/ or user systemd directories.

False Positives

Provisioning scripts may do this intentionally, but it should not happen implicitly from a shared executable hook.

Remediation

Remove systemd registration from the hook and keep service installation in an explicit reviewed provisioning step.