YARA rule 'backdoor_persistence': Backdoor persistence with malicious payloads (shell commands, SSH key injection, hidden root users) [malware]
- Category
- YARA Match
- Confidence
- 75% confidence
- Finding
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
- Content
md orrect across timezones and DST. ## The pattern to set up The whole design is two scheduled entries: 1. **The wrapped job** - the real task, run through `wrap`, on its normal schedule. 2. **The watchdog** - `check` on a short schedule (e.g. every 30 min) that pipes its output to wherever the user gets notified. `crontab` prints both lines. Show them to the user and let the user add them with `crontab -e`. Never run `crontab`, edit crontab files, or create scheduled tasks yourself. In OpenClaw, suggest the two scheduled tasks (the wrapped command, and a short-interval `check` whose output routes to their channel), show exactly what each would run, and create them only if the user explicitly confirms. ## How to help 1. **Setting up a new schedule:** ask for the command, how often it should run, and whether retries make sense (yes for anything network-dependent). Then produce the wrapped crontab line via `crontab`, and explain the watchdog line. Always set `--expect-every` - without
