Carbanak+FIN7
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
11.A.3
|
|
|
A Technique detection named "Microsoft Office application launched Mshta.exe via lnk file" (Red) was generated when winword.exe spawned mshta.exe via an lnk file.
[1]
[2]
|
|
A Technique detection named "Executed suspicious JavaScript or VBScript via mshta application" (Orange) was generated when suspicoius script was executed via mshta.exe.
[1]
|
|
|
|
A Technique detection named "Executed mshta application" (Blue) was generated when winword.exe spawned mshta.exe.
[1]
|
|
A Technique detection named "MSHTA acting as VBScript Interpreter" (Yellow) was generated when mshta.exe was used to execute in-line VBScript.
[1]
|
|
winword.exe spawns mshta.exe
-
File Monitoring
-
Process Monitoring
[1]
[2]
winword.exe spawns mshta.exe
[1]
winword.exe spawns mshta.exe
[1]
winword.exe spawns mshta.exe
[1]
winword.exe spawns mshta.exe
-
Process Monitoring
-
DLL Monitoring
[1]
APT29
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
20.A.1
|
|
|
Telemetry showed rundll32.exe executing kxwn.lock.
[1]
|
|
A Technique alert detection (orange; medium risk) called "Rundll32" was generated due to rundll32.exe executing kxwn.lock.
[1]
|
|
Executed Run key persistence payload on user login using RunDll32
rundll32.exe executing kxwn.lock
[1]
Executed Run key persistence payload on user login using RunDll32
rundll32.exe executing kxwn.lock
[1]
APT3
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
1.A.1.2
|
|
|
Specific Behavior alerts were generated based on suspicious indicators that a \"Loaded non-DLL and non-CPL file with specified parameters via rundll32.\" The alerts were tagged with the correct ATT&CK Tactic (Defense Evasion, Execution) and Technique (Rundll32).
[1]
[2]
[3]
|
|
Telemetry showed cmd.exe executing update.dat via rundll32.exe. The telemetry was tainted by a trace detection on Resume Viewer.exe.
[1]
[2]
[3]
|
|
Previously executed batch file (pdfhelper.cmd) launched a DLL payload (update.dat) using Rundll32
[1]
[2]
[3]
Previously executed batch file (pdfhelper.cmd) launched a DLL payload (update.dat) using Rundll32
[1]
[2]
[3]