Carbanak+FIN7
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
5.C.3
|
|
|
A Technique detection named "Service Execution" was generated when cmd.exe spawned from a service executable in C:\Windows\.
[1]
|
|
|
|
16.A.6
|
|
|
|
|
A Technique detection named "Service Execution" was generated when PAExec-7856-hotelmanager.exe was started.
[1]
|
|
cmd.exe spawns from a service executable in C:\Windows\
[1]
cmd.exe spawns from a service executable in C:\Windows\
[1]
Windows service started PAExec-{PID}-HOTELMANAGER.exe, which executes hollow.exe
[1]
Windows service started PAExec-{PID}-HOTELMANAGER.exe, which executes hollow.exe
[1]
APT29
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
8.C.3
|
|
|
Telemetry showed PSEXECSVC.exe executing python.exe.
[1]
|
|
An MSSP detection for "Service Execution" occurred containing evidence of PSEXECSVC.exe executing python.exe.
[1]
|
|
A Technique alert detection for "PsExec interacted with services - SONAR.PsExeSvc!gen1" was generated on PsExecSvc targeting python.exe.
[1]
|
|
10.A.1
|
|
|
Minimum detection criteria was not met for this procedure.
|
|
Executed python.exe using PSExec
python.exe spawned by PSEXESVC.exe
[1]
Executed python.exe using PSExec
python.exe spawned by PSEXESVC.exe
[1]
Executed python.exe using PSExec
python.exe spawned by PSEXESVC.exe
[1]
Executed persistent service (javamtsup) on system startup
javamtsup.exe spawning from services.exe