Potential COM Object Hijacking Via TreatAs Subkey - Registry
Detects COM object hijacking via TreatAs subkey
Sigma rule (View on GitHub)
1title: Potential COM Object Hijacking Via TreatAs Subkey - Registry
2id: 9b0f8a61-91b2-464f-aceb-0527e0a45020
3status: test
4description: Detects COM object hijacking via TreatAs subkey
5references:
6 - https://bohops.com/2018/08/18/abusing-the-com-registry-structure-part-2-loading-techniques-for-evasion-and-persistence/
7author: Kutepov Anton, oscd.community
8date: 2019-10-23
9modified: 2023-02-07
10tags:
11 - attack.persistence
12 - attack.t1546.015
13logsource:
14 category: registry_add
15 product: windows
16detection:
17 selection:
18 EventType: 'CreateKey' # Don't want DeleteKey events
19 TargetObject|contains|all:
20 - 'HKU\'
21 - 'Classes\CLSID\'
22 - '\TreatAs'
23 filter_svchost:
24 # Example of target object by svchost
25 # TargetObject: HKU\S-1-5-21-1098798288-3663759343-897484398-1001_Classes\CLSID\{0003000A-0000-0000-C000-000000000046}\TreatAs
26 Image: 'C:\WINDOWS\system32\svchost.exe'
27 condition: selection and not 1 of filter_*
28falsepositives:
29 - Maybe some system utilities in rare cases use linking keys for backward compatibility
30level: medium
References
Related rules
- COM Hijacking via TreatAs
- Potential PSFactoryBuffer COM Hijacking
- Potential Persistence Using DebugPath
- Potential Persistence Via Scrobj.dll COM Hijacking
- Rundll32 Registered COM Objects