T1588.005 Splunk · SPL

Detect Exploits in Splunk

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/

SPL Detection Query

Splunk (SPL)
spl
index=wineventlog sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
  (ParentImage="*\\winword.exe" OR ParentImage="*\\excel.exe" OR ParentImage="*\\powerpnt.exe"
   OR ParentImage="*\\outlook.exe" OR ParentImage="*\\mspub.exe" OR ParentImage="*\\onenote.exe"
   OR ParentImage="*\\msaccess.exe" OR ParentImage="*\\acrord32.exe" OR ParentImage="*\\acrobat.exe"
   OR ParentImage="*\\chrome.exe" OR ParentImage="*\\firefox.exe"
   OR ParentImage="*\\msedge.exe" OR ParentImage="*\\iexplore.exe"
   OR ParentImage="*\\java.exe" OR ParentImage="*\\javaw.exe" OR ParentImage="*\\javaws.exe")
  (Image="*\\cmd.exe" OR Image="*\\powershell.exe" OR Image="*\\pwsh.exe"
   OR Image="*\\wscript.exe" OR Image="*\\cscript.exe" OR Image="*\\mshta.exe"
   OR Image="*\\rundll32.exe" OR Image="*\\regsvr32.exe" OR Image="*\\certutil.exe"
   OR Image="*\\bitsadmin.exe" OR Image="*\\msiexec.exe" OR Image="*\\wmic.exe"
   OR Image="*\\msbuild.exe" OR Image="*\\installutil.exe" OR Image="*\\regasm.exe")
| eval CommandLineLower=lower(CommandLine)
| eval NetworkIndicator=if(match(CommandLineLower, "(http://|https://|ftp://|invoke-webrequest|net\.webclient|downloadstring|downloadfile|start-bitstransfer|curl |wget )"), 1, 0)
| eval CredentialAccess=if(match(CommandLineLower, "(mimikatz|lsass|sekurlsa|ntds|procdump|comsvcs|minidump|vaultcmd)"), 1, 0)
| eval PersistenceIndicator=if(match(CommandLineLower, "(schtasks|reg add|currentversion.run|startup|userinit|sc create|sc config)"), 1, 0)
| eval LateralMovement=if(match(CommandLineLower, "(psexec|wmiexec|winrm|net use|enter-pssession|invoke-command)"), 1, 0)
| eval ExploitScore=NetworkIndicator + CredentialAccess + PersistenceIndicator + LateralMovement + 1
| table _time, host, User, Image, CommandLine, ParentImage, ParentCommandLine,
        NetworkIndicator, CredentialAccess, PersistenceIndicator, LateralMovement, ExploitScore
| sort - ExploitScore - _time
high severity medium confidence

Detects exploit-based process chains using Sysmon Event ID 1 (Process Creation) by identifying shells and scripting engines spawned from commonly exploited client-side applications. Covers the full Office suite, Adobe Acrobat, major browsers (Chrome, Firefox, Edge, IE), and Java runtimes — all frequent targets of client-side exploit delivery. Each matching event is scored by follow-on behavioral indicators to help analysts prioritize: base score of 1 for any suspicious spawn, with additional points for network callback patterns, credential access tools, persistence mechanisms, and lateral movement commands.

Data Sources

Process: Process CreationSysmon Event ID 1

Required Sourcetypes

XmlWinEventLog:Microsoft-Windows-Sysmon/Operational

False Positives & Tuning

  • Office macros used in legitimate business automation (e.g., Excel VBA launching cmd.exe for data exports, report generation, or ERP integrations)
  • Browser extensions, enterprise SSO agents, or print/download helper objects that legitimately spawn child processes
  • PDF processing integrations where Acrobat invokes system utilities for digital signature validation, document conversion, or secure print workflows
  • Java-based enterprise applications (ERP, HR, financial platforms) that spawn OS-level commands for file operations or external integrations
Download portable Sigma rule (.yml)

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections