Analysis
-
max time kernel
150s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
09-03-2024 14:44
Static task
static1
Behavioral task
behavioral1
Sample
bc11bb90169faacb26d050a77affb70e.exe
Resource
win7-20240221-en
Behavioral task
behavioral2
Sample
bc11bb90169faacb26d050a77affb70e.exe
Resource
win10v2004-20240226-en
General
-
Target
bc11bb90169faacb26d050a77affb70e.exe
-
Size
258KB
-
MD5
bc11bb90169faacb26d050a77affb70e
-
SHA1
beee17fa7f05f5f09fd032233593853c29c2713d
-
SHA256
026bb2ca37ff474af2d065e49f28db8239b527caf72cc66a01186a75215a07a3
-
SHA512
4042cc11793b5ef89961b32e5d9fbd73ee03d604b317ef663e323aa17a509662038dc818b6fcee61ff5c53bfb49c5c736e51d8e0981337b8cc280f27a0de0adf
-
SSDEEP
6144:hpWsjilAKubzU4TJQHXbAl4UZCAZYyNiCRPUICt30t:hpWsjilAKubzUouHrRqCq/hCIWo
Malware Config
Extracted
xtremerat
egimegi.no-ip.biz
Signatures
-
Detect XtremeRAT payload 7 IoCs
resource yara_rule behavioral2/memory/3160-3-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3160-4-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3160-6-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3160-7-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1592-8-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3160-9-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1592-10-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat -
XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3016 set thread context of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 2 IoCs
pid pid_target Process procid_target 860 1592 WerFault.exe 89 4704 1592 WerFault.exe 89 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3016 bc11bb90169faacb26d050a77affb70e.exe -
Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3016 wrote to memory of 3160 3016 bc11bb90169faacb26d050a77affb70e.exe 88 PID 3160 wrote to memory of 1592 3160 bc11bb90169faacb26d050a77affb70e.exe 89 PID 3160 wrote to memory of 1592 3160 bc11bb90169faacb26d050a77affb70e.exe 89 PID 3160 wrote to memory of 1592 3160 bc11bb90169faacb26d050a77affb70e.exe 89 PID 3160 wrote to memory of 1592 3160 bc11bb90169faacb26d050a77affb70e.exe 89 PID 3160 wrote to memory of 640 3160 bc11bb90169faacb26d050a77affb70e.exe 90 PID 3160 wrote to memory of 640 3160 bc11bb90169faacb26d050a77affb70e.exe 90 PID 3160 wrote to memory of 640 3160 bc11bb90169faacb26d050a77affb70e.exe 90
Processes
-
C:\Users\Admin\AppData\Local\Temp\bc11bb90169faacb26d050a77affb70e.exe"C:\Users\Admin\AppData\Local\Temp\bc11bb90169faacb26d050a77affb70e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3016 -
C:\Users\Admin\AppData\Local\Temp\bc11bb90169faacb26d050a77affb70e.exeC:\Users\Admin\AppData\Local\Temp\bc11bb90169faacb26d050a77affb70e.exe2⤵
- Suspicious use of WriteProcessMemory
PID:3160 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:1592
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1592 -s 4804⤵
- Program crash
PID:860
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1592 -s 4884⤵
- Program crash
PID:4704
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:640
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1592 -ip 15921⤵PID:2108
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 1592 -ip 15921⤵PID:3388