Techniques
Sample rules
Windows Command Line Obfuscation Via Superscript Characters
- source: splunk
- technicques:
Description
The following analytic detects Windows system binaries executed with command line arguments that contain superscript or modifier letter characters (for example the Unicode characters used in “/ᵖᵃckᵃge”) in place of regular ASCII letters. Windows command line parsers such as msiexec.exe normalize these look-alike characters, so the argument still works while evading string-based detections. This technique has been observed in ClickFix-style campaigns where victims paste a command into the Run dialog that silently installs a remote MSI package with msiexec.exe.
Detection logic
| tstats `security_content_summariesonly`
count min(_time) as firstTime
max(_time) as lastTime
FROM datamodel=Endpoint.Processes WHERE
Processes.process_path = "*:\\Windows\\*"
NOT Processes.process_name IN (
"backgroundTaskHost.exe",
"csrss.exe",
"csrss.exe",
"dllhost.exe",
"lsass.exe",
"msedgewebview2.exe",
"RuntimeBroker.exe",
"SensorRuntimeBroker.exe",
"services.exe",
"sihost.exe",
"smss.exe",
"svchost.exe",
"taskhostw.exe",
"wininit.exe",
"winlogon.exe",
"WmiPrvSE.exe",
"WUDFHost.exe"
)
by Processes.action Processes.dest Processes.original_file_name
Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
Processes.process Processes.process_exec Processes.process_guid Processes.process_hash
Processes.process_id Processes.process_integrity_level Processes.process_name Processes.process_path
Processes.user Processes.user_id Processes.vendor_product
| `drop_dm_object_name(Processes)`
| regex process="(?:\\-\\-
|/)(?:[a-zA-Z0-9]+)?[\\x{1D00}-\\x{1D7F}\\x{02B0}-\\x{02FF}\\x{1D80}-\\x{1DBF}\\x{2070}-\\x{209F}\\x{FF00}-\\x{FFEF}]+(?:[a-zA-Z0-9]+)?"
| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `windows_command_line_obfuscation_via_superscript_characters_filter`