Analysis
-
max time kernel
134s -
max time network
139s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
02-11-2024 11:47
Static task
static1
Behavioral task
behavioral1
Sample
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe
Resource
win7-20240903-en
General
-
Target
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe
-
Size
49KB
-
MD5
8174a96006f2acd6ae72b8e8b1657690
-
SHA1
df00f51fb1bbbe8a8f0726411cc9650906ee1553
-
SHA256
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def
-
SHA512
5a0486afc6e218583694fddb210c23d2591c038a8c6ee57226eddf1aaf20f16e139f0d617e54900a78061fe59aad88917d1487b83c662738f945bd7c7f9afd7d
-
SSDEEP
1536:zD5gnDtYxE0moj5O/rDjvmKILPmqV0s2koOqjeN:vaD8EJJDD7jm5Cq
Malware Config
Extracted
xtremerat
franco1.no-ip.org
Signatures
-
Detect XtremeRAT payload 5 IoCs
Processes:
resource yara_rule behavioral2/memory/4860-10-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4860-9-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1744-11-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4860-12-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1744-13-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
Processes:
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exedescription pid process target process PID 2300 set thread context of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe -
Processes:
resource yara_rule behavioral2/memory/4860-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4860-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4860-10-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4860-9-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1744-11-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4860-12-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1744-13-0x0000000010000000-0x000000001004D000-memory.dmp upx -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 2 IoCs
Processes:
WerFault.exeWerFault.exepid pid_target process target process 1916 1744 WerFault.exe svchost.exe 4916 1744 WerFault.exe svchost.exe -
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.
Processes:
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exesvchost.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language svchost.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exepid process 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe -
Suspicious use of WriteProcessMemory 15 IoCs
Processes:
7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exedescription pid process target process PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 2300 wrote to memory of 4860 2300 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe PID 4860 wrote to memory of 1744 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe svchost.exe PID 4860 wrote to memory of 1744 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe svchost.exe PID 4860 wrote to memory of 1744 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe svchost.exe PID 4860 wrote to memory of 1744 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe svchost.exe PID 4860 wrote to memory of 2976 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe msedge.exe PID 4860 wrote to memory of 2976 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe msedge.exe PID 4860 wrote to memory of 2976 4860 7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe msedge.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe"C:\Users\Admin\AppData\Local\Temp\7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2300 -
C:\Users\Admin\AppData\Local\Temp\7de3054bae0aa73e5ceebca435aea90f62b6a3401b989bb5118bbaf89fb33def.exe
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:4860 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵
- System Location Discovery: System Language Discovery
PID:1744 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1744 -s 4804⤵
- Program crash
PID:1916
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1744 -s 4884⤵
- Program crash
PID:4916
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2976
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1744 -ip 17441⤵PID:5108
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 512 -p 1744 -ip 17441⤵PID:4432