Carbanak+FIN7
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
5.C.3
|
|
Technique
(Configuration Change (Detection Logic))
|
A Technique detection named "T1569.002 Service Execution" was generated when cmd.exe spawns from a service executable in C:\Windows\.
[1]
[2]
|
|
|
|
16.A.6
|
|
|
|
|
A Technique detection named "ServiceExecuted" (Info) was generated when Windows service started PAExec-{PID}-HOTELMANAGER.exe.
[1]
|
|
cmd.exe spawns from a service executable in C:\Windows\
[1]
[2]
cmd.exe spawns from a service executable in C:\Windows\
[1]
[2]
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
|
|
|
A General alert detection called "PSExecLateralMovement" was generated for unusual markers of PSExec being used for lateral movement.
[1]
|
|
Telemetry showed PSEXESVC.exe with command-line arguments to execute python.exe. The detection was correlated to a parent alert on rcs.3aka3.doc for the execution of a rogue unusual executable.
[1]
[2]
|
|
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]
[2]
Executed persistent service (javamtsup) on system startup
javamtsup.exe spawning from services.exe