T1547.009 Microsoft Sentinel · KQL

Detect Shortcut Modification in Microsoft Sentinel

Adversaries may create or modify shortcuts that can execute a program during system boot or user login. Shortcuts (.lnk files) or symbolic links are used to reference other files or programs that will be opened or executed when the shortcut is clicked or executed by a system startup process. Adversaries may abuse shortcuts in the startup folder to execute their tools and achieve persistence. They may also edit the target path or entirely replace existing shortcuts so their malware executes instead of the intended legitimate program. Threat actors including Lazarus Group, APT39, Leviathan, and Turla have used this technique. LNK browser extensions may also be modified to persistently launch malware.

MITRE ATT&CK

Tactic
Persistence Privilege Escalation
Technique
T1547 Boot or Logon Autostart Execution
Sub-technique
T1547.009 Shortcut Modification
Canonical reference
https://attack.mitre.org/techniques/T1547/009/

KQL Detection Query

Microsoft Sentinel (KQL)
kusto
DeviceFileEvents
| where Timestamp > ago(24h)
| where FileName endswith ".lnk"
| where FolderPath has_any ("Start Menu\\Programs\\Startup", "Start Menu\\Programs\\StartUp")
   or ActionType == "FileModified" and FolderPath has "Start Menu"
| project Timestamp, DeviceName, ActionType, FileName, FolderPath, SHA256,
         InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountName
| sort by Timestamp desc
high severity high confidence

Detects creation or modification of .lnk shortcut files in Windows Startup folders. Covers both per-user (%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup) and system-wide (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp) locations. Also detects modifications to existing shortcuts in the Start Menu that could redirect legitimate application launches.

Data Sources

File: File CreationFile: File ModificationMicrosoft Defender for Endpoint

Required Tables

DeviceFileEvents

False Positives & Tuning

  • Software installations that create legitimate startup shortcuts (VPN clients, communication tools)
  • User-created shortcuts pinned to the Start Menu or placed in Startup folder intentionally
  • Windows Updates or application updates that recreate or modify existing shortcuts
  • Enterprise deployment tools (SCCM, Intune) deploying shortcuts during provisioning
Download portable Sigma rule (.yml)

Other platforms for T1547.009


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Create Malicious Shortcut in Startup Folder

    Expected signal: Sysmon Event ID 11: FileCreate for df00tech-test.lnk in the Startup folder. Sysmon Event ID 1: PowerShell process creation with WScript.Shell COM object usage.

  2. Test 2Modify Existing Shortcut Target

    Expected signal: Sysmon Event ID 11: FileCreate for the initial shortcut. File modification event when the target path is changed. Both events show PowerShell as the initiating process.

  3. Test 3Create VBScript Shortcut in Startup

    Expected signal: Sysmon Event ID 11 for both the .vbs file creation and the .lnk shortcut in Startup. The shortcut targeting wscript.exe with a .vbs argument is a strong malicious indicator.

Unlock Pro Content

Get the full detection package for T1547.009 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections