Windows findstr Launches .lnk via Command Line

Flags find.exe or findstr.exe processes whose command lines end with a .lnk file.

FreeReviewedSigma · Medium · v2
Product
windows
Category
process_creation
Author
Trent Liffick (SigmaHQ), DRL 1.1
Published
2020-05-01
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 Windows process executions where find.exe or findstr.exe are started and their command line ends with a .lnk reference. An attacker can use living-off-the-land utilities to enumerate and trigger shortcut files, which can lead to follow-on execution. The detection relies on process creation telemetry, specifically the executable image name and the command line ending in a .lnk path or quoted .lnk value.

Related detections9 linkedT1036 — drag to rearrange
Windows renamed dctask64.exe execution via known IMPHASH values
Suspicious Rclone Exfiltration Masquerading as wininit.exe
Suspicious Executable Running from Public Pictures Directory
Suspicious Python Execution via Renamed Synaptics Binary
Agent Tesla Persistence via Realtek Named Scheduled Task Batch
Suspicious Interlock Fake Updater Executable Execution
Malicious User Account Created by a Computer Account (via security)
Suspicious Execution of agent.exe From WinSyncDefender AppData Directory (via process_creation)
Malicious Scheduled Task Masquerading as Auto Update via schtasks (via process_creation)
Windows findstr Launches .lnk via Command Line
Pivot detection · T1036 · 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.