Hacktool Execution - PE Metadata
Detects the execution of different Windows based hacktools via PE metadata (company, product, etc.) even if the files have been renamed
Sigma rule (View on GitHub)
1title: Hacktool Execution - PE Metadata
2id: 37c1333a-a0db-48be-b64b-7393b2386e3b
3status: test
4description: Detects the execution of different Windows based hacktools via PE metadata (company, product, etc.) even if the files have been renamed
5references:
6 - https://github.com/cube0x0
7 - https://www.virustotal.com/gui/search/metadata%253ACube0x0/files
8author: Florian Roth (Nextron Systems)
9date: 2022-04-27
10modified: 2024-01-15
11tags:
12 - attack.credential-access
13 - attack.resource-development
14 - attack.t1588.002
15 - attack.t1003
16logsource:
17 category: process_creation
18 product: windows
19detection:
20 selection:
21 Company: 'Cube0x0' # Detects the use of tools created by a well-known hacktool producer named "Cube0x0", which includes his handle in all binaries as company information in the PE headers (SharpPrintNightmare, KrbRelay, SharpMapExec, etc.)
22 condition: selection
23falsepositives:
24 - Unlikely
25level: high
References
Related rules
- Mimikatz Command Line With Ticket Export
- OpenCanary - MSSQL Login Attempt Via SQLAuth
- OpenCanary - MSSQL Login Attempt Via Windows Authentication
- OpenCanary - MySQL Login Attempt
- OpenCanary - REDIS Action Command Attempt