ATT&CK coverage › Technique

Hide Artifacts: Hidden Window T1564.003

Adversaries may use hidden windows to conceal malicious activity from the plain sight of users. In some cases, windows that would typically be displayed when an application carries out an operation can be hidden. This may be utilized by system administrators to avoid disrupting user work environments when carrying out administrative tasks.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing4688A new process has been created.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 8 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (4 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
CommandLine7match 7--headless, \Contacts\, -sta , :\Perflogs\, http
Image4ends_with 4, match 1, starts_with 1\chrome.exe, \opera.exe, \vivaldi.exe, \cmd.exe, C:\Program Files\WindowsApps\Microsoft.MicrosoftEdge
OriginalFileName3eq 3Cmd.Exe, CONHOST.EXE, AdvancedRun.exe
ScriptBlockText1match 1:\Program Files\Amazon\WorkSpacesConfig\Scripts\, $PSScriptRoot\Module\WorkspaceScriptModule\WorkspaceScriptModule, WindowStyle

Top indicator values (86 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
CommandLinematch--headless45
Imageends_with\msedge.exe222
Imageends_with\vivaldi.exe219
Imageends_with\brave.exe220
Imageends_with\chrome.exe211
Imageends_with\opera.exe221
CommandLinematchstart/b1
CommandLinematch.ps113
CommandLinematch\Temporary Internet\1
CommandLinematch.vbs15
CommandLinematch\inetpub\1
CommandLinematch\Contacts\16
CommandLinematch/min"1
CommandLinematch/min 1
CommandLinematch.vbe14
CommandLinematch-noni 1
CommandLinematch.scr15
CommandLinematch:\Perflogs\14
CommandLinematch\Favorites\16
CommandLinematch\AppData\Roaming\110

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 8 rules