Analysis
-
max time kernel
154s -
max time network
164s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
04-12-2022 03:00
Static task
static1
Behavioral task
behavioral1
Sample
dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe
Resource
win10v2004-20220812-en
General
-
Target
dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe
-
Size
536KB
-
MD5
f9669d139ea87703d4f818f596e2380a
-
SHA1
273e9e376e1872e0edec7e67f75cf539f7ff4173
-
SHA256
dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b
-
SHA512
a9ec32c90822c721b3a54651418c936abaf4337c58278604e03567cf2c4bbc51e753405532a125e63695eb8fbecba2a35019e7525d39ac1e88b9eddd4112aad5
-
SSDEEP
3072:11qI8JDKei598pR0d4uj+1JE7t4XGKLZtw7HdJMuTSnZ1db4ri:jqwpZ+Z1db4
Malware Config
Extracted
xtremerat
ax0.no-ip.biz
�mrjoo.no-ip.info
jomeka.no-ip.biz
Signatures
-
Detect XtremeRAT payload 6 IoCs
resource yara_rule behavioral2/memory/3044-141-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/3044-142-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3044-143-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3044-145-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3044-146-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3044-147-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat -
XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
-
resource yara_rule behavioral2/memory/4844-135-0x0000000000400000-0x0000000000451000-memory.dmp upx behavioral2/memory/4844-137-0x0000000000400000-0x0000000000451000-memory.dmp upx behavioral2/memory/4844-138-0x0000000000400000-0x0000000000451000-memory.dmp upx behavioral2/memory/4844-144-0x0000000000400000-0x0000000000451000-memory.dmp upx -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 2232 set thread context of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 4844 set thread context of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe -
Suspicious use of WriteProcessMemory 24 IoCs
description pid Process procid_target PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 2232 wrote to memory of 4844 2232 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 80 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 4844 wrote to memory of 3044 4844 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 81 PID 3044 wrote to memory of 3296 3044 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 82 PID 3044 wrote to memory of 3296 3044 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 82 PID 3044 wrote to memory of 3296 3044 dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe"C:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2232 -
C:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe"C:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4844 -
C:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exeC:\Users\Admin\AppData\Local\Temp\dcf0426cf8452536d86428a5a1ae8a43a21a38fa74fb9b5e80f3b26f1976d56b.exe3⤵
- Suspicious use of WriteProcessMemory
PID:3044 -
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"4⤵PID:3296
-
-
-