Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-06-08
Updated
2026-08-28

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects the workplace init script executing deploy_new.py which the actor used for persistence on a compromised SonicWall SMA appliance. The 0-day exploitation established a boot-time service under /etc/init.d/workplace to relaunch attacker tooling after reboots. Boot persistence on an internet-facing appliance provides durable access that survives restarts and patching attempts.

Related detections9 linkedT1543 — drag to rearrange
Malicious BRICKSTORM Backdoor Execution via Masqueraded Binary Path
Malicious Linux XorDDoS gcc.pid Device Marker File via file_event
Windows Code Integrity: Blocked Driver Load Due to Revoked Certificate (Event ID 3023)
Windows PUA System Informer Driver Load via SystemInformer.sys
System Informer Execution on Windows Process Creation
Windows Driver Load: Process Hacker (processhacker.sys) Presence
Windows Code Integrity blocked image/driver loads due to signature level or policy violations
Windows Process Hacker Execution Identified by Image Metadata and Hashes
Windows: Service Created by System Using Client with PID 0 (SCM Event 7045)
Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py
Pivot detection · T1543 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.