Suspicious systemd User Service Persistence miasma-monitor (via file_event)

PremiumReviewedSigma · High · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-06-07
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 creation of a miasma-monitor systemd user service unit used by the M-Red-Team AsyncAPI compromise for persistence. Writing a user-level systemd service lets an attacker relaunch a monitoring implant on login without root. The specific unit name combined with the user systemd path is a strong persistence signal.

Related detections9 linkedT1543.002 — drag to rearrange
Malicious Systemd Service Masquerading as Sd-Pam Helper
Malicious Linux systemd Persistence nvmconf.service
Suspicious Linux Persistence via sed Edit of Boot and Init Files
Suspicious systemd Service Persistence via GRIDTIDE xapt
Suspicious Python Execution of Fake Sysmon Script From Config Directory
Suspicious Linux Boot Persistence via rc.local or init.d Modification (via file_event)
Malicious systemd-daemon Masquerading Binary Execution on Linux
Suspicious Masquerading systemd Unit display-managerd Creation via File System
Suspicious Systemd Service Unit Written to System Directory (via process_creation)
Suspicious systemd User Service Persistence miasma-monitor (via file_event)
Pivot detection · T1543.002 · 9 related

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