meltedinhex/analyst-ai-pack / skills/hunting-persistence-on-linux
hunting-persistence-on-linux
FlaggedHunts for Linux persistence by inspecting cron, systemd units, shell rc files, SSH authorized_keys, and common autostart locations for attacker-added entries. Activates for requests to hunt Linux persistence, audit cron/systemd for backdoors, or find unauthorized autostart and authorized_keys entries.
Hunting Persistence on Linux
When to Use
- You have collected Linux persistence-relevant files (cron entries, systemd units, shell rc
files,
authorized_keys, autostart) and want to flag suspicious entries. - You are triaging a suspected compromised Linux host's persistence surface.
Do not use this on a live root shell as a substitute for proper IR collection — feed it collected copies. It reads files statically and executes nothing.
Prerequisites
- Collected persistence artifacts (cron files, unit files, rc files,
authorized_keys).
Safety & Handling
- Read files statically; treat their contents as untrusted.
Workflow
Step 1: Scan persistence files
python scripts/analyst.py scan /path/to/collected
Recursively scans known persistence locations and flags entries containing download/exec patterns
(curl|wget ... | sh, base64 -d | bash, reverse-shell one-liners, nc -e), suspicious paths
(/tmp, /dev/shm), and unexpected authorized_keys additions.
Step 2: Categorize by mechanism
Group findings by mechanism: cron, systemd, rc/profile, SSH keys, autostart.
Step 3: Confirm
Compare against a known-good baseline of expected services/keys; investigate deviations.
Step 4: Document
Record each persistence entry, its mechanism, and the suspicious indicator.
Validation
- Findings are grouped by persistence mechanism.
- Reverse-shell/download-exec one-liners are flagged with the matched pattern.
authorized_keysadditions are surfaced for review.
Pitfalls
- Legitimate admin cron/systemd entries — baseline before alerting.
- Persistence in less-common spots (udev, PAM, LD_PRELOAD) not covered by basic scans.
- Encoded/obfuscated payloads hiding the true command.
References
- See
references/api-reference.mdfor the scanner. - ATT&CK T1543.002 and T1053.003 (linked in frontmatter).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |