Carbanak+FIN7
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
7.C.4
|
|
|
|
|
A Technique detection named "Anomaly detected in ASEP registry" (Medium) was generated when the Java-Update subkey added to HKLM\Software\Microsoft\Windows\CurrentVersion\Run was identified as a Registry run key Autostart Extensibility Point (ASEP).
[1]
|
|
10.A.4
|
|
|
A Technique detection named "Suspicious RemoteAccessToolInRunKey was detected" (Low) was generated when remote access software was added as a Registry run key.
[1]
|
|
Java-Update subkey is added to HKLM\Software\Microsoft\Windows\CurrentVersion\Run
-
Process Monitoring
-
Windows Registry
[1]
Java-Update subkey is added to HKLM\Software\Microsoft\Windows\CurrentVersion\Run
-
Process Monitoring
-
Windows Registry
[1]
msiexec.exe adds the tvncontrol subkey in HKLM\Software\Microsoft\CurrentVersion\Run
-
Process Monitoring
-
Windows Registry
[1]
APT29
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
5.B.1
|
|
General
(Alert, Correlated)
|
A General alert detection (low severity) was generated for "a link file (LNK) with unusual characteristics was opened." This detection was correlated to a parent General detection that rcs.3aka3.doc was identified as a patpoopy.backdoor.
[1]
|
Technique
(Correlated, Alert)
|
A Technique alert detection (medium severity) for Registry Run Keys/Startup Folder was generated due to the file write of hostui.lnk in the Startup folder. This detection was correlated to a parent General detection of rcs.3aka3.doc being identified as 'patpoopy' backdoor.
[1]
|
|
An MSSP detection for Persistence was generated due to hostui.lnk being placed inside the Startup folder.
[1]
|
|
10.B.1
|
|
|
Minimum detection criteria was not met for this procedure.
|
|
11.A.11
|
|
|
Telemetry showed powershell.exe adding Run key persistence into the Registry.
[1]
|
|
An MSSP detection for Execution was generated containing evidence a Registry key was created for persistence under HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.
[1]
[2]
|
|
Created a LNK file (hostui.lnk) in the Startup folder that executes on login
powershell.exe creating the file hostui.lnk in the Startup folder
[1]
Created a LNK file (hostui.lnk) in the Startup folder that executes on login
powershell.exe creating the file hostui.lnk in the Startup folder
[1]
Created a LNK file (hostui.lnk) in the Startup folder that executes on login
powershell.exe creating the file hostui.lnk in the Startup folder
[1]
Executed LNK payload (hostui.lnk) in Startup Folder on user login
Evidence that the file hostui.lnk (which executes hostui.bat as a byproduct) was executed from the Startup Folder
-
This activity would have been blocked by Microsoft Defender.
Established Registry Run key persistence using PowerShell
Addition of the Webcache subkey in HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
[1]
Established Registry Run key persistence using PowerShell
Addition of the Webcache subkey in HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
[1]
[2]
APT3
|
Step
|
ATT&CK Pattern
|
Detection Type |
Detection Note |
|
1.B.1
|
|
|
Telemetry showed the execution sequence for Resume Viewer.exe writing autoupdate.bat to Debbie's Startup folder to establish persistence.
[1]
|
|
10.A.1
|
|
|
Telemetry showed the execution sequence of cmd.exe executing autoupdate.bat from the Startup folder to start update.dat.
[1]
|
|
Previously executed batch file (pdfhelper.cmd) moved a separate batch file (autoupdate.bat) to the Startup folder
[1]
Batch file (autoupdate.bat) previously written to Startup folder executed when user Debbie logs on to Nimda (10.0.1.6), launching a DLL payload (update.dat) using Rundll32
[1]