Analysis
- max time kernel
92s - max time network
115s - platform
windows10-2004_x64 - resource
win10v2004-20240221-en - resource tags
arch:x64arch:x86image:win10v2004-20240221-enlocale:en-usos:windows10-2004-x64system - submitted
24/02/2024, 17:58
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
a264e27d62ebe7928bf39ce92d6a9293.exe
Resource
win7-20240220-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
a264e27d62ebe7928bf39ce92d6a9293.exe
Resource
win10v2004-20240221-en
8 signatures
150 seconds
General
- Target a264e27d62ebe7928bf39ce92d6a9293.exe
- Size 93KB
- Sample240224-wkcdaaah9w
- SHA256 068f005d603e86227683dc2489c26aaa898232d6c76b75f221f3815fc7fa508d
- MD5 a264e27d62ebe7928bf39ce92d6a9293
- SHA1 e2f984642a80861f7461339d158726762e55484b
- SHA512 2ce781a56570a6492dc1607627393a3cf956d201851397ec88eb234d8557de05df0fbe898ade6e6e2d2ebed3c90c097ba7151a0815c596e7cd845b83ac62e808
- SSDEEP 1536:LoQgvnH7Q+U4sqkn4gCrvSYyCvckT7aNxhBs+BTf8o5VZ8j8C:fgvnH7Hj9gCDXvPT70xhBs+9fvIjB
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
xtremerat
C2
-
franco1.no-ip.org
Signatures
- Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/3472-5-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3472-6-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3916-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3472-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3916-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/3472-2-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3472-4-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3472-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3472-6-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3916-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3472-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3916-9-0x0000000010000000-0x000000001004D000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2912 set thread context of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.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 4532 3916 WerFault.exe 87 2896 3916 WerFault.exe 87 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2912 a264e27d62ebe7928bf39ce92d6a9293.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 2912 wrote to memory of 3472 2912 a264e27d62ebe7928bf39ce92d6a9293.exe 86 PID 3472 wrote to memory of 3916 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 87 PID 3472 wrote to memory of 3916 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 87 PID 3472 wrote to memory of 3916 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 87 PID 3472 wrote to memory of 3916 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 87 PID 3472 wrote to memory of 2412 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 88 PID 3472 wrote to memory of 2412 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 88 PID 3472 wrote to memory of 2412 3472 a264e27d62ebe7928bf39ce92d6a9293.exe 88
Processes
-
C:\Users\Admin\AppData\Local\Temp\a264e27d62ebe7928bf39ce92d6a9293.exe"C:\Users\Admin\AppData\Local\Temp\a264e27d62ebe7928bf39ce92d6a9293.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2912 -
C:\Users\Admin\AppData\Local\Temp\a264e27d62ebe7928bf39ce92d6a9293.exeC:\Users\Admin\AppData\Local\Temp\a264e27d62ebe7928bf39ce92d6a9293.exe2⤵
- Suspicious use of WriteProcessMemory
PID:3472 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:3916
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3916 -s 4804⤵
- Program crash
PID:4532
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3916 -s 4884⤵
- Program crash
PID:2896
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2412
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 360 -p 3916 -ip 39161⤵PID:2660
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 480 -p 3916 -ip 39161⤵PID:3924