Analysis
- max time kernel
149s - max time network
151s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
18/03/2024, 01:17
Behavioral task
behavioral1
Sample
d235200959c52eabf6c6ea17f263ffc5.exe
Resource
win7-20240221-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
d235200959c52eabf6c6ea17f263ffc5.exe
Resource
win10v2004-20240226-en
8 signatures
150 seconds
General
- Target d235200959c52eabf6c6ea17f263ffc5.exe
- Size 68KB
- Sample240318-bnwacach36
- SHA256 49118dcbfda46094e8a0590ee2c67c8e02a10ef00a5ce52b74b13309194f1f9f
- MD5 d235200959c52eabf6c6ea17f263ffc5
- SHA1 35f9bef2606beeaa3451f2a2e043baf595333d18
- SHA512 8fb487d04d31fcfa69e9d178af1d4ae5fa02c6654c9a4626b6d4cc91e4690fbe0e94da2be95a1f5434f410ac1bb4c560c4f1d71e8d373c33276e7371abdbfaa0
- SSDEEP 1536:noccWrucPPawodS2DKjAYNOgL1+ZVnmMrf/7/T/8E4MDpa:oTW9PPXoFDKnNOgJkVX/7/T/Xa
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
xtremerat
C2
-
maillia.no-ip.biz
Signatures
- Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/5712-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/5712-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/220-9-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/5712-10-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/220-11-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/3688-0-0x0000000000400000-0x0000000000416000-memory.dmp upx behavioral2/memory/5712-3-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/5712-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3688-6-0x0000000000400000-0x0000000000416000-memory.dmp upx behavioral2/memory/5712-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/5712-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/220-9-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/5712-10-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/220-11-0x0000000010000000-0x000000001004D000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3688 set thread context of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 - 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 5856 220 WerFault.exe 90 876 220 WerFault.exe 90 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3688 d235200959c52eabf6c6ea17f263ffc5.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 3688 wrote to memory of 5712 3688 d235200959c52eabf6c6ea17f263ffc5.exe 89 PID 5712 wrote to memory of 220 5712 d235200959c52eabf6c6ea17f263ffc5.exe 90 PID 5712 wrote to memory of 220 5712 d235200959c52eabf6c6ea17f263ffc5.exe 90 PID 5712 wrote to memory of 220 5712 d235200959c52eabf6c6ea17f263ffc5.exe 90 PID 5712 wrote to memory of 220 5712 d235200959c52eabf6c6ea17f263ffc5.exe 90 PID 5712 wrote to memory of 4916 5712 d235200959c52eabf6c6ea17f263ffc5.exe 93 PID 5712 wrote to memory of 4916 5712 d235200959c52eabf6c6ea17f263ffc5.exe 93 PID 5712 wrote to memory of 4916 5712 d235200959c52eabf6c6ea17f263ffc5.exe 93
Processes
-
C:\Users\Admin\AppData\Local\Temp\d235200959c52eabf6c6ea17f263ffc5.exe"C:\Users\Admin\AppData\Local\Temp\d235200959c52eabf6c6ea17f263ffc5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3688 -
C:\Users\Admin\AppData\Local\Temp\d235200959c52eabf6c6ea17f263ffc5.exe"C:\Users\Admin\AppData\Local\Temp\d235200959c52eabf6c6ea17f263ffc5.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:5712 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:220
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 220 -s 4804⤵
- Program crash
PID:5856
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 220 -s 5044⤵
- Program crash
PID:876
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4916
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 220 -ip 2201⤵PID:4172
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 540 -p 220 -ip 2201⤵PID:1596