Analysis
-
max time kernel
157s -
max time network
168s -
platform
windows10-2004_x64 -
resource
win10v2004-20220414-en -
submitted
25-06-2022 06:58
Static task
static1
Behavioral task
behavioral1
Sample
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe
Resource
win7-20220414-en
Behavioral task
behavioral2
Sample
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe
Resource
win10v2004-20220414-en
General
-
Target
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe
-
Size
262KB
-
MD5
62d4dc40fba011645eba8418f7f65537
-
SHA1
f9d2a45f7d547eef3dd730e9b91f53ad7f7ee4f6
-
SHA256
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082
-
SHA512
3f425a897f87a880bd672d2e427bd82c9a5f002666b5d646aada2e5a3b0762d15edeaf8b2e004930515954e646614c04d58c0e34892e53ceffe25ca56c461d58
Malware Config
Signatures
-
suricata: ET MALWARE Ransomware Locky CnC Beacon 21 May
suricata: ET MALWARE Ransomware Locky CnC Beacon 21 May
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exedescription pid process target process PID 4480 set thread context of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exedescription pid process target process PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe PID 4480 wrote to memory of 540 4480 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe 3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe"C:\Users\Admin\AppData\Local\Temp\3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4480 -
C:\Users\Admin\AppData\Local\Temp\3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe"C:\Users\Admin\AppData\Local\Temp\3a0da8dcfc1a1d02d6a4fa69a43c48546ec97545005d2917ca32075c8d51d082.exe"2⤵PID:540
-