Suspicious PIF Persistence File in Public Libraries (via file_event)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-10-02
Updated
2026-10-02

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 DBatLoader writing its packed payload as a PIF file into the Users Public Libraries directory, which it references from a url shortcut for persistence. Program information files placed in this location are not produced by legitimate software. The file enables the loader to relaunch after reboot.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious OCEANMAP EdgeContext.url Startup Persistence (via file_event)
Suspicious GhostSocks Run Key Persistence to AppData Cache via registry_set
Suspicious Run Key Persistence Masquerading as NVIDIA Driver Update
Suspicious Run Key Persistence Executing system.bat via registry_set
Malicious Run Key Persistence Masquerading as Windows Update
Suspicious Run Key Persistence Under Masquerading Service Names
Suspicious Run Key Persistence With Masqueraded System Binary by Millenium RAT (via registry_set)
Suspicious Autostart Persistence via Run Key Pointing Outside Program Files (via registry_set)
Suspicious RunOnce Persistence Relaunching Payload with Safe Mode Flag
Suspicious PIF Persistence File in Public Libraries (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.