Detect Exploits in Elastic Security
Adversaries may buy, steal, or download exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than developing their own exploits, an adversary may find, modify, or purchase exploits from online sources, exploit vendors, criminal marketplaces (including exploit kits), or from other threat actors. Adversaries such as Ember Bear have obtained exploitation scripts against publicly-disclosed vulnerabilities from public repositories, while Kimsuky has obtained exploit code for various CVEs. Acquired exploits may be used across multiple phases of the adversary lifecycle including initial access, privilege escalation, defense evasion, credential access, and lateral movement. Because the acquisition of exploits occurs entirely on adversary-controlled infrastructure, direct detection is not possible from victim telemetry — detection must focus on observable indicators when those acquired exploits are deployed.
MITRE ATT&CK
- Tactic
- Resource Development
- Technique
- T1588 Obtain Capabilities
- Sub-technique
- T1588.005 Exploits
- Canonical reference
- https://attack.mitre.org/techniques/T1588/005/
Elastic Detection Query
process where event.type == "start" and
process.parent.name : (
"winword.exe", "excel.exe", "powerpnt.exe", "outlook.exe",
"mspub.exe", "onenote.exe", "msaccess.exe",
"acrord32.exe", "acrobat.exe",
"chrome.exe", "firefox.exe", "msedge.exe", "iexplore.exe",
"java.exe", "javaw.exe", "javaws.exe"
) and
process.name : (
"cmd.exe", "powershell.exe", "pwsh.exe",
"wscript.exe", "cscript.exe", "mshta.exe",
"rundll32.exe", "regsvr32.exe", "certutil.exe",
"bitsadmin.exe", "msiexec.exe", "wmic.exe",
"msbuild.exe", "installutil.exe", "regasm.exe",
"regsvcs.exe", "schtasks.exe"
)
/* Priority filter: require at least one high-confidence indicator to reduce noise */
and process.command_line : (
"*http://*", "*https://*", "*ftp://*",
"*Invoke-WebRequest*", "*Net.WebClient*", "*DownloadString*", "*DownloadFile*",
"*Start-BitsTransfer*", "*curl *", "*wget *",
"*mimikatz*", "*sekurlsa*", "*lsass*", "*ntds*",
"*procdump*", "*comsvcs*", "*MiniDump*", "*vaultcmd*",
"*schtasks*", "*reg add*", "*CurrentVersion\\Run*",
"*sc create*", "*sc config*", "*startup*", "*userinit*",
"*psexec*", "*wmiexec*", "*winrm*", "*net use*",
"*Enter-PSSession*", "*Invoke-Command*"
)Detects potential deployment of acquired exploits (T1588.005) by identifying suspicious child processes spawned from commonly exploited applications — Office suite, PDF readers, browsers, and Java runtimes. Matches the parent-child process chain used in known exploit chains. The command-line filter requires at least one post-exploitation indicator (network callback, credential access, persistence, or lateral movement) to reduce false positives. Analysts should correlate ExploitScore-equivalent signals by reviewing process.command_line contents across the four indicator categories.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate Office macros executing PowerShell for IT automation tasks such as data export, report generation, or SharePoint interaction via approved scripts
- Adobe Acrobat or Reader launching cmd.exe or msiexec.exe during plugin installation, print driver configuration, or PDF conversion workflows
- Enterprise Java applications (e.g., Eclipse, IntelliJ, Confluence) spawning cmd.exe or PowerShell as part of build processes, Maven/Gradle tasks, or integrated terminal features
- Browser-based enterprise tools (e.g., Citrix, SAP web clients) launching native executables as registered protocol handlers or helper applications
- Chrome or Edge launching msiexec.exe for browser extension installation via enterprise policies
Other platforms for T1588.005
Testing Methodology
Validate this detection against 5 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.
- Test 1Simulate Document Exploit Process Chain (cmd Reconnaissance)
Expected signal: Sysmon Event ID 1: Process Create with Image=cmd.exe. CommandLine contains 'whoami', 'hostname', 'ipconfig', 'net user'. Security Event ID 4688 (with command line auditing enabled) records the same. When run from a Word macro, InitiatingProcessFileName=winword.exe triggers the detection's parent-child matching logic.
- Test 2Simulate Browser Exploit Network Callback (Stage-2 Download Cradle)
Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with CommandLine containing 'Net.WebClient', 'DownloadString', and the target URL. Sysmon Event ID 3: Network Connection attempt to 192.0.2.1:4444 (TEST-NET-1 per RFC 5737 — safe non-routable address that generates telemetry without reaching any real host). PowerShell ScriptBlock Log Event ID 4104 captures the full script content.
- Test 3VBScript-Based Exploit Payload Simulation
Expected signal: Sysmon Event ID 1 (x2): First for powershell.exe creating the VBS file, second for wscript.exe executing it. The char()-based obfuscation in the VBS content mimics obfuscation patterns used in real exploit-delivered payloads. Sysmon Event ID 11: File Create event for the VBS file dropped to TEMP. PowerShell ScriptBlock Log Event ID 4104 for the PowerShell wrapper.
- Test 4Exploit Guard ASR Rule Configuration Audit
Expected signal: PowerShell ScriptBlock Log Event ID 4104 for the MpPreference query. Informational output to file showing which ASR rules are active. When ASR rules are in block mode and a real Office application attempts to spawn a child process (e.g., via a macro), Windows Defender Operational log generates Event ID 1121 (Blocked) or Event ID 1122 (Audit) with the rule GUID and process details.
- Test 5Simulate Post-Exploit Process Access (Sysmon Event ID 10)
Expected signal: Sysmon Event ID 10 (ProcessAccess): SourceImage=powershell.exe, TargetImage=notepad.exe, GrantedAccess=0x0410 (PROCESS_QUERY_INFORMATION | PROCESS_VM_READ). Sysmon Event ID 1: powershell.exe process create. The 0x0410 access mask is characteristic of credential dumping tools and shellcode injection staging — many SIEM rules alert on this mask from non-system processes targeting sensitive processes.
References (10)
- https://attack.mitre.org/techniques/T1588/005/
- https://www.exploit-db.com/
- https://citizenlab.ca/2016/08/million-dollar-dissident-iphone-zero-day-nso-group-uae/
- https://www.nytimes.com/2013/07/14/world/europe/nations-buying-as-hackers-sell-computer-flaws.html
- https://www.wired.co.uk/article/darkhotel-hacking-team-cyber-espionage
- https://learn.microsoft.com/en-us/microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference
- https://learn.microsoft.com/en-us/defender-endpoint/advanced-hunting-deviceprocessevents-table
- https://learn.microsoft.com/en-us/defender-endpoint/advanced-hunting-deviceevents-table
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1203/T1203.md
- https://www.microsoft.com/en-us/security/blog/2021/07/15/protecting-customers-from-a-private-sector-offensive-actor-using-0-day-exploits-and-devilstongue-malware/
Unlock Pro Content
Get the full detection package for T1588.005 including response playbook, investigation guide, and atomic red team tests.