Analysis
-
max time kernel
94s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system -
submitted
07/03/2024, 20:26
Static task
static1
Behavioral task
behavioral1
Sample
b9940e38ac42648f958a2f8b8cdd2935.exe
Resource
win7-20240215-en
Behavioral task
behavioral2
Sample
b9940e38ac42648f958a2f8b8cdd2935.exe
Resource
win10v2004-20231215-en
General
-
Target
b9940e38ac42648f958a2f8b8cdd2935.exe
-
Size
284KB
-
MD5
b9940e38ac42648f958a2f8b8cdd2935
-
SHA1
3bcffc2b201b8da00a5c3e848582ebd2f2bfb130
-
SHA256
d369022b5849f8f785ada5468a198643f39aa29f8007037d0aef37df92f9c3f0
-
SHA512
57c072f71a08c9bbfb455e19eb23fc08a4b6094eb6b25ca271fb6b4b062464b702088d207c8b24f75245947a921b3d08f719b5376dfa690b38aeeec68d57387a
-
SSDEEP
6144:snpAOgw8HYWO9UGBvVoYGrLHXiugVn+ut9o3aQ1dUDR7Y+Xt5u:snpH4HYWO9Dm9g+W9VQdC7YX
Malware Config
Extracted
xtremerat
far3on.zapto.org
Signatures
-
Detect XtremeRAT payload 7 IoCs
resource yara_rule behavioral2/memory/2816-14-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2816-15-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2816-17-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2816-19-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3588-21-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2816-22-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3588-23-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 4892 set thread context of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 -
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 3012 3588 WerFault.exe 86 2636 3588 WerFault.exe 86 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4892 b9940e38ac42648f958a2f8b8cdd2935.exe -
Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 4892 wrote to memory of 2816 4892 b9940e38ac42648f958a2f8b8cdd2935.exe 85 PID 2816 wrote to memory of 3588 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 86 PID 2816 wrote to memory of 3588 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 86 PID 2816 wrote to memory of 3588 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 86 PID 2816 wrote to memory of 3588 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 86 PID 2816 wrote to memory of 4880 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 87 PID 2816 wrote to memory of 4880 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 87 PID 2816 wrote to memory of 4880 2816 b9940e38ac42648f958a2f8b8cdd2935.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\b9940e38ac42648f958a2f8b8cdd2935.exe"C:\Users\Admin\AppData\Local\Temp\b9940e38ac42648f958a2f8b8cdd2935.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4892 -
C:\Users\Admin\AppData\Local\Temp\b9940e38ac42648f958a2f8b8cdd2935.exe"C:\Users\Admin\AppData\Local\Temp\b9940e38ac42648f958a2f8b8cdd2935.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2816 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:3588
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3588 -s 4804⤵
- Program crash
PID:3012
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3588 -s 4884⤵
- Program crash
PID:2636
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4880
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3588 -ip 35881⤵PID:1884
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 3588 -ip 35881⤵PID:1276