Analysis
-
max time kernel
104s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20231222-en -
resource tags
arch:x64arch:x86image:win10v2004-20231222-enlocale:en-usos:windows10-2004-x64system -
submitted
28-01-2024 01:04
Static task
static1
Behavioral task
behavioral1
Sample
7bc0b174e48004a50e25ebda53a3cf37.exe
Resource
win7-20231215-en
Behavioral task
behavioral2
Sample
7bc0b174e48004a50e25ebda53a3cf37.exe
Resource
win10v2004-20231222-en
General
-
Target
7bc0b174e48004a50e25ebda53a3cf37.exe
-
Size
161KB
-
MD5
7bc0b174e48004a50e25ebda53a3cf37
-
SHA1
77e2bf1ebd2c00b813611f6dfb9d27543f47556e
-
SHA256
a8f2f2e3c271f145e75770cbc67fedc52a34b96e80dc289cbe2c66ec6ffb176f
-
SHA512
887f5af59b7f7bd350b3da759e4f484c224827b204561584e9870c012fbc25cbeb12e7a2a5dacf1541767e66eda922080d6a69ed1cda100a2339017524081453
-
SSDEEP
3072:SdNy+xmahW4fRPHKPZjIk+jQ01aaQnn0KBzWnCn2gqQ1osyRuQ8:aQYRfCZjIkWQ01aRnn0KBUDqNKuQ8
Malware Config
Extracted
xtremerat
xsstrema.no-ip.org
Signatures
-
Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/3920-6-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3920-5-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/2716-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3920-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/2716-9-0x0000000010000000-0x000000001004D000-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/3920-2-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3920-4-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3920-6-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3920-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2716-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3920-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2716-9-0x0000000010000000-0x000000001004D000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2268 set thread context of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 -
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 4124 2716 WerFault.exe 89 2368 2716 WerFault.exe 89 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2268 7bc0b174e48004a50e25ebda53a3cf37.exe -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 2268 wrote to memory of 3920 2268 7bc0b174e48004a50e25ebda53a3cf37.exe 86 PID 3920 wrote to memory of 2716 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 89 PID 3920 wrote to memory of 2716 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 89 PID 3920 wrote to memory of 2716 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 89 PID 3920 wrote to memory of 2716 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 89 PID 3920 wrote to memory of 3816 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 91 PID 3920 wrote to memory of 3816 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 91 PID 3920 wrote to memory of 3816 3920 7bc0b174e48004a50e25ebda53a3cf37.exe 91
Processes
-
C:\Users\Admin\AppData\Local\Temp\7bc0b174e48004a50e25ebda53a3cf37.exe"C:\Users\Admin\AppData\Local\Temp\7bc0b174e48004a50e25ebda53a3cf37.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2268 -
C:\Users\Admin\AppData\Local\Temp\7bc0b174e48004a50e25ebda53a3cf37.exeC:\Users\Admin\AppData\Local\Temp\7bc0b174e48004a50e25ebda53a3cf37.exe2⤵
- Suspicious use of WriteProcessMemory
PID:3920 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:2716
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2716 -s 4804⤵
- Program crash
PID:4124
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2716 -s 4884⤵
- Program crash
PID:2368
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:3816
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 2716 -ip 27161⤵PID:2044
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 504 -p 2716 -ip 27161⤵PID:3540