Detection rules › Kusto Query Language

MosaicLoader

Source
upstream

This query looks Malware Hides Itself Among Windows Defender Exclusions to Evade Detection.

MITRE ATT&CK coverage

TacticTechniques
Defense EvasionT1562 Impair Defenses

Event coverage

ProviderEvent IDTitle
Sysmon13RegistryEvent (Value Set)
Security-Auditing4657A registry value was modified.
Defender-DeviceRegistryEvents9005003Registry value set

Stages and Predicates

Stage 1: source

DeviceRegistryEvents

Stage 2: where

and
  or
    RegistryKey starts_with "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Defender\\Exclusions\\Extensions"
    RegistryKey starts_with "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Defender\\Exclusions\\Processes"
    RegistryKey starts_with "HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Windows Defender\\\\Exclusions\\\\Paths"
  ActionType eq "RegistryValueSet"

Stage 3: extend

Stage 4: extend

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
ActionTypeeq
  • RegistryValueSet
RegistryKeystarts_with
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\Extensions
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Exclusions\Processes
  • HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Defender\\Exclusions\\Paths