huntrule

Windows: Alerts on Creation of .sed Self-Extraction Directive File

Flags creation of newly created .sed directive files on Windows, which can be used for self-extracting package abuse.

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

ATT&CK techniques

Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags when a new file is created with a filename ending in “.sed”, which are Self Extraction Directive files. Attackers may abuse Windows packaging workflows to place directives into unexpected files, sometimes embedding PE content associated with the directive. Telemetry required is Windows file creation/executable file creation events that include the target filename.

Reporting behind it

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: Alerts on Creation of .sed Self-Extraction Directive File
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.