IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Suspicious WMI Image Load from MS Office Suspicious WerFault Child Process »
Elastic Docs ›Elastic Security Solution [7.16] ›Detections and alerts ›Prebuilt rule reference

Suspicious WMIC XSL Script Execution

edit

Suspicious WMIC XSL Script Execution

edit

Identifies WMIC whitelisting bypass techniques by alerting on suspicious execution of scripts. When WMIC loads scripting libraries it may be indicative of a whitelist bypass.

Rule type: eql

Rule indices:

  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: medium

Risk score: 21

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Defense Evasion

Version: 2 (version history)

Added (Elastic Stack release): 7.10.0

Last modified (Elastic Stack release): 7.12.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
sequence by process.entity_id with maxspan = 2m [process where
event.type in ("start", "process_started") and (process.name :
"WMIC.exe" or process.pe.original_file_name : "wmic.exe") and
process.args : ("format*:*", "/format*:*", "*-format*:*") and not
process.command_line : "* /format:table *"] [library where event.type
== "start" and dll.name : ("jscript.dll", "vbscript.dll")]

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 2 (7.12.0 release)

  • Updated query, changed from:

    sequence by process.entity_id with maxspan=2m [process where
event.type in ("start", "process_started") and (process.name :
"WMIC.exe" or process.pe.original_file_name == "wmic.exe") and
wildcard(process.args, "format*:*", "/format*:*", "*-format*:*") and
not wildcard(process.command_line, "* /format:table *")] [library
where event.type == "start" and file.name in ("jscript.dll",
"vbscript.dll")]
« Suspicious WMI Image Load from MS Office Suspicious WerFault Child Process »