Analysis
-
max time kernel
94s -
max time network
98s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
21-01-2025 21:49
Static task
static1
Behavioral task
behavioral1
Sample
ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe
Resource
win7-20240708-en
General
-
Target
ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe
-
Size
256KB
-
MD5
23e402752135e6088a8c7b8d2e22749d
-
SHA1
33f88f7b9f393d8c130303f1d55d3a96564e6a32
-
SHA256
ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692
-
SHA512
07aa02d7b6a162667e214c384a6f61bdf31421c3346dc87f2587a74daa2c1822f9a0e95f5b78d928b1b17c156303bc25be4b5ab3144b356cf31371a702c511e2
-
SSDEEP
3072:L9rfiQUSKDtXxJGPztG1U9VhIHZ+U9yB+M1/y2tVjjPvmtgq7I:hDc1U9VhIHZ+U9yoMc0jjPvmtgp
Malware Config
Extracted
xtremerat
ssaaiq.no-ip.org
Signatures
-
Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/2264-5-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/2264-6-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4604-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/2264-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4604-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.
-
Xtremerat family
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 116 set thread context of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 -
resource yara_rule behavioral2/memory/2264-2-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2264-4-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2264-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2264-6-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4604-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/2264-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4604-9-0x0000000010000000-0x000000001004D000-memory.dmp upx -
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 324 4604 WerFault.exe 84 4884 4604 WerFault.exe 84 -
System Location Discovery: System Language Discovery 1 TTPs 3 IoCs
Attempt gather information about the system language of a victim in order to infer the geographical location of that host.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language svchost.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 116 wrote to memory of 2264 116 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 83 PID 2264 wrote to memory of 4604 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 84 PID 2264 wrote to memory of 4604 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 84 PID 2264 wrote to memory of 4604 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 84 PID 2264 wrote to memory of 4604 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 84 PID 2264 wrote to memory of 4020 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 85 PID 2264 wrote to memory of 4020 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 85 PID 2264 wrote to memory of 4020 2264 ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe"C:\Users\Admin\AppData\Local\Temp\ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:116 -
C:\Users\Admin\AppData\Local\Temp\ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exeC:\Users\Admin\AppData\Local\Temp\ac13208a40f105f511d2185b4712599a3041cd188ff18b8693d55dc74a32f692.exe2⤵
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2264 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵
- System Location Discovery: System Language Discovery
PID:4604 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4604 -s 4884⤵
- Program crash
PID:324
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4604 -s 5084⤵
- Program crash
PID:4884
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4020
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4604 -ip 46041⤵PID:5112
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 516 -p 4604 -ip 46041⤵PID:4712