Suspicious Ousaban Installation Marker maisum.dat Created (via file_event)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-09-24
Updated
2026-09-24

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 Ousaban banking trojan dropping its empty installation marker file maisum.dat whose creation time records the infection timestamp alongside the payload directory. Creation of this specific marker file indicates a successful install. The trojan then persists through a Run key.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Winos Persistence Binary Created as ProgramData BITTS2.exe (via process_creation)
Suspicious Shahmaran Autostart Masquerading as Adobe Updater
Suspicious K7Soft Autostart Persistence
Suspicious Run Key Persistence to svcghost in Public WPSManager Path via Registry
Malicious Startup LNK Dropped by WinRAR via CVE-2025-8088 Path Traversal
Suspicious Run Key Persistence Masquerading as MicrosoftUpdate via Axios npm Compromise
Suspicious Startup Persistence via Registry Run Key Pointing to Script
Suspicious User Shell Folders Startup Redirect for Persistence via Registry
Malicious XRed Backdoor Execution from ProgramData Synaptics Path (via process_creation)
Suspicious Ousaban Installation Marker maisum.dat Created (via file_event)
Pivot detection · T1547.001 · 9 related

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