Windows Self Extraction Directive (.sed) File Created in Suspicious Paths

Alerts on .sed directive file creation under ProgramData/Temp/Tasks paths on Windows, consistent with iExpress-based packaging abuse.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
Joseliyo Sanchez, @Joseliyo_Jstnk (SigmaHQ), DRL 1.1
Published
2024-02-05
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags creation events for self extraction directive files ending in .sed when the target filename is located under common attacker-preferred directories such as ProgramData, Temp, AppData Local Temp, and Windows Tasks folders. These .sed files can be consumed by iExpress (iexpress.exe) to build self-extracting packages, and their placement in sensitive or temporary paths can indicate staging or stealthy packaging. The detection relies on Windows file creation telemetry that includes the TargetFilename and supports substring and suffix matching.

Related detections9 linkedT1218 — drag to rearrange
Suspicious .NET LOLBin Execution via CasPol or RegAsm
Possible DarkGate DLL Sideloading via iTunesHelper Loading CoreFoundation
Suspicious extrac32 CAB Extraction Abuse
Malicious cdb.exe Masquerading as fontdrvhost in ProgramData (via process_creation)
Malicious certutil Decodehex Payload Reconstruction by DarkGate
Malicious MSIX Package Execution via App Installer ms-appinstaller Protocol (via process_creation)
Malicious ViPNet Backdoor Loader via lumpdiag.exe Path Substitution
Suspicious BitLockerToGo Execution from Unusual Parent
Suspicious Proxy Execution via pcalua
Windows Self Extraction Directive (.sed) File Created in Suspicious Paths
Pivot detection · T1218 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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