SigmaHQ/rules/windows/malware/win_mal_ursnif.yml
megan201296 eb8a0636c5
Update win_mal_ursnif.yml
After @thomaspatzke changed to HKU, I did some reading. HKU is for HKEY_User, not HKEY_Current_User (what this threat is tied to. However, he was correct that HKCU does not exist as a prefix for sysmon (see the notes section under event id 13 here: https://github.com/SwiftOnSecurity/sysmon-config/blob/master/sysmonconfig-export.xml). Changed to ignore the key name, confirmed that the key is still uniique.
2019-04-14 11:51:13 -05:00

23 lines
668 B
YAML

title: Ursnif
status: experimental
description: Detects new registry key created by Ursnif malware.
references:
- https://blog.yoroi.company/research/ursnif-long-live-the-steganography/
- https://blog.trendmicro.com/trendlabs-security-intelligence/phishing-campaign-uses-hijacked-emails-to-deliver-ursnif-by-replying-to-ongoing-threads/
tags:
- attack.execution
- attack.t1112
author: megan201296
date: 2019/02/13
logsource:
product: windows
service: sysmon
detection:
selection:
EventID: 13
TargetObject: '*\Software\AppDataLow\Software\Microsoft\\*'
condition: selection
falsepositives:
- Unknown
level: critical