Analysis
-
max time kernel
94s -
max time network
96s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
02-12-2024 05:40
Static task
static1
Behavioral task
behavioral1
Sample
85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe
Resource
win7-20240729-en
General
-
Target
85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe
-
Size
78KB
-
MD5
00244dcc0c1460553b1ff2ac7ee68d6d
-
SHA1
8593d6f3ed291c5de66b9240a24f34d5e023c635
-
SHA256
85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a
-
SHA512
62dd536fdbe9655056ffb818f1fd29ba3245e2273e6fbc0aef4bf0359fe1faf7af988f48356a8a51bfbca3af5bb8368cc17794a667b7aaf03a66680fcff708fe
-
SSDEEP
1536:077SPQgf9iuZlf2/dYTeqyLWWa+Amx9BgTme+mjA4O8WI3rLY31gHNh+IuxzkY9S:0FmapMWInY314uJkf
Malware Config
Extracted
xtremerat
oktayemre.dyndns.biz
Signatures
-
Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/1680-5-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1680-6-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1896-7-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1680-8-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/1896-9-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.
-
Xtremerat family
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4972 set thread context of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 -
resource yara_rule behavioral2/memory/1680-2-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1680-4-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1680-5-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1680-6-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1896-7-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1680-8-0x0000000010000000-0x000000001004A000-memory.dmp upx behavioral2/memory/1896-9-0x0000000010000000-0x000000001004A000-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 3748 1896 WerFault.exe 84 3400 1896 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 svchost.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 4972 wrote to memory of 1680 4972 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 83 PID 1680 wrote to memory of 1896 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 84 PID 1680 wrote to memory of 1896 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 84 PID 1680 wrote to memory of 1896 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 84 PID 1680 wrote to memory of 1896 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 84 PID 1680 wrote to memory of 4188 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 85 PID 1680 wrote to memory of 4188 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 85 PID 1680 wrote to memory of 4188 1680 85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe 85
Processes
-
C:\Users\Admin\AppData\Local\Temp\85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe"C:\Users\Admin\AppData\Local\Temp\85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4972 -
C:\Users\Admin\AppData\Local\Temp\85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exeC:\Users\Admin\AppData\Local\Temp\85e73de5470443c5f5a23823f9afba835ad37fd7480eaf618287c6b31e6a8b3a.exe2⤵
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:1680 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵
- System Location Discovery: System Language Discovery
PID:1896 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1896 -s 4804⤵
- Program crash
PID:3748
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1896 -s 4884⤵
- Program crash
PID:3400
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4188
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1896 -ip 18961⤵PID:2036
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 528 -p 1896 -ip 18961⤵PID:3068