Part of epic #1171.
π Problem Statement
The GlassWorm-style detector (#1150/PR #1169, plus #1172/#1173/#1174) covers how a worm spreads
(self_propagation), what it hides its payload with (unicode_steganography), and β pending
#1173 β what it's after (credential_targeting). It has no signal for a fourth common worm/dropper
behavior: making itself survive a reboot or a fresh shell session by registering itself in a
well-known auto-run location.
π― Objective
Add a signal that fires when source code writes to one of a bounded set of well-known auto-run
registration points:
- Shell profile files (
~/.bashrc, ~/.zshrc, ~/.profile) β specifically an append to these,
not just any reference to the filename
crontab (via crontab - piping, or direct writes to /etc/cron.d/, /var/spool/cron/)
- systemd user unit files (
~/.config/systemd/user/*.service)
- PowerShell
$PROFILE (append/write)
- Windows registry
Run/RunOnce keys (HKCU\...\Run, reg add ... /v ... /d)
π οΈ Proposed Implementation
New THREAT_SIGNATURES entry (working name: persistence_registration) matching a write/append
call whose target path or key matches the bounded list above. Follow the same discipline as
self_propagation: the target must be the literal argument to a write/append call, not just
present somewhere nearby in the file, to keep false positives near zero (dotfile management tools,
shell-config generators, and systemd unit templating are all real, legitimate use cases that
reference these same paths).
β
Acceptance Criteria
Part of epic #1171.
π Problem Statement
The GlassWorm-style detector (#1150/PR #1169, plus #1172/#1173/#1174) covers how a worm spreads
(
self_propagation), what it hides its payload with (unicode_steganography), and β pending#1173 β what it's after (
credential_targeting). It has no signal for a fourth common worm/dropperbehavior: making itself survive a reboot or a fresh shell session by registering itself in a
well-known auto-run location.
π― Objective
Add a signal that fires when source code writes to one of a bounded set of well-known auto-run
registration points:
~/.bashrc,~/.zshrc,~/.profile) β specifically an append to these,not just any reference to the filename
crontab(viacrontab -piping, or direct writes to/etc/cron.d/,/var/spool/cron/)~/.config/systemd/user/*.service)$PROFILE(append/write)Run/RunOncekeys (HKCU\...\Run,reg add ... /v ... /d)π οΈ Proposed Implementation
New
THREAT_SIGNATURESentry (working name:persistence_registration) matching a write/appendcall whose target path or key matches the bounded list above. Follow the same discipline as
self_propagation: the target must be the literal argument to a write/append call, not justpresent somewhere nearby in the file, to keep false positives near zero (dotfile management tools,
shell-config generators, and systemd unit templating are all real, legitimate use cases that
reference these same paths).
β Acceptance Criteria
systemd-unit/PowerShell-profile/registry-Run-key
reads
.bashrcto check its contents, or a templating tool generating a systemd unit fileas a build artifact rather than writing directly to the live path) must not fire
language-cruciblecorpus: zero unintended hits before thegolden-master rebless