PowerShell Creating Startup .lnk Shortcut Persistence (Windows File Events)

Detects PowerShell writing .lnk files into the Windows Startup folder, a common persistence mechanism.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Christopher Peacock '@securepeacock', SCYTHE (SigmaHQ), DRL 1.1
Published
2021-10-24
Updated
2026-07-31

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 identifies instances where PowerShell or pwsh writes shortcut files (.lnk) to a Windows Startup location. Attackers commonly use Startup shortcuts to achieve persistence by automatically launching malicious code when a user signs in. It relies on Windows file event telemetry capturing process image name and the target file path containing Startup and ending with .lnk.

Related detections9 linkedT1547.001 — drag to rearrange
Suspicious Run Key Persistence Named AppResolver (via registry_set)
Suspicious SystemBC Persistence via Run Key to ProgramData Script
Suspicious Interlock RAT Persistence via HKCU Run Key Registration to AppData Payload (via process_creation)
Suspicious SOCKS Proxy Persistence via SystemBC PowerShell Run Key
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Malicious Startup Persistence via WindowsDefenderSync Shortcut (via file_event)
Malicious PXA Stealer Persistence via Windows Update Service Run Key (via registry_set)
Suspicious NetSupport client32 Persistence via Run Key from ProgramData
Suspicious Run Key Persistence Named NvidiaDriverUpdate (via registry_set)
PowerShell Creating Startup .lnk Shortcut Persistence (Windows File Events)
Pivot detection · T1547.001 · 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.