Analysis
-
max time kernel
133s -
max time network
123s -
platform
windows10-2004_x64 -
resource
win10v2004-20241007-en -
resource tags
arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system -
submitted
23-10-2024 23:51
Static task
static1
Behavioral task
behavioral1
Sample
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe
Resource
win7-20241010-en
General
-
Target
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe
-
Size
84KB
-
MD5
6a58f94b6553712c2f3b80174aa26051
-
SHA1
637304d1bd170f500123a212209e6931bb037f6e
-
SHA256
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328
-
SHA512
3891ff5aa9d0d0716d7b3fc91d890a68a4a826a7cc4aa0a61a0793b933c6f0211b84bc3477ea67145ee169aaecfd6b04daf60db4e765290f3139e24462469718
-
SSDEEP
1536:fG2EnTramCVTJ10e9yhVugW1FAAzWCb4pqZ1m4e2ggJ0x:fynvBCVTJ10ey0gW8AzWCbmqZ8ABA
Malware Config
Extracted
xtremerat
qwertyuiop.no-ip.biz
Signatures
-
Detect XtremeRAT payload 5 IoCs
Processes:
resource yara_rule behavioral2/memory/5100-8-0x0000000010000000-0x0000000010049000-memory.dmp family_xtremerat behavioral2/memory/5100-7-0x0000000010000000-0x0000000010049000-memory.dmp family_xtremerat behavioral2/memory/5064-10-0x0000000010000000-0x0000000010049000-memory.dmp family_xtremerat behavioral2/memory/5100-11-0x0000000010000000-0x0000000010049000-memory.dmp family_xtremerat behavioral2/memory/5064-12-0x0000000010000000-0x0000000010049000-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
Processes:
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exedescription pid process target process PID 4872 set thread context of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe -
Processes:
resource yara_rule behavioral2/memory/5100-3-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5100-6-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5100-8-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5100-7-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5064-10-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5100-11-0x0000000010000000-0x0000000010049000-memory.dmp upx behavioral2/memory/5064-12-0x0000000010000000-0x0000000010049000-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 4068 5064 WerFault.exe svchost.exe 1868 5064 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:
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exesvchost.exea47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exedescription ioc process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language svchost.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exedescription pid process Token: SeDebugPrivilege 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe -
Suspicious use of WriteProcessMemory 15 IoCs
Processes:
a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exea47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exedescription pid process target process PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 4872 wrote to memory of 5100 4872 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe PID 5100 wrote to memory of 5064 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe svchost.exe PID 5100 wrote to memory of 5064 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe svchost.exe PID 5100 wrote to memory of 5064 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe svchost.exe PID 5100 wrote to memory of 5064 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe svchost.exe PID 5100 wrote to memory of 2704 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe msedge.exe PID 5100 wrote to memory of 2704 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe msedge.exe PID 5100 wrote to memory of 2704 5100 a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe msedge.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe"C:\Users\Admin\AppData\Local\Temp\a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4872 -
C:\Users\Admin\AppData\Local\Temp\a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe"C:\Users\Admin\AppData\Local\Temp\a47ce9e3c73e01ff95100faef7b414d26d8570f87fce3c0c72b863847bdc3328.exe"2⤵
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:5100 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵
- System Location Discovery: System Language Discovery
PID:5064 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5064 -s 4804⤵
- Program crash
PID:4068
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5064 -s 4884⤵
- Program crash
PID:1868
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2704
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 5064 -ip 50641⤵PID:3896
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 5064 -ip 50641⤵PID:904