Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
209s -
max time network
249s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
25/11/2022, 19:53
Static task
static1
Behavioral task
behavioral1
Sample
a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe
Resource
win10v2004-20221111-en
General
-
Target
a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe
-
Size
898KB
-
MD5
c6063f1ebf76cb261d34cc179842a3d1
-
SHA1
0cd817f26d148deb12148254b7814e83ba90cd56
-
SHA256
a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5
-
SHA512
ca13fb6dc08d94cc8a7be2a0b88a449495447eb3fdf2efd0b26811304effeae876df8481aa653e4f8a9addf8afc6748ead50d596d23d6bfebfb10957624175e3
-
SSDEEP
12288:Itb20Qc3lT7af41ePBRYuQLKpqeUhbTv5OFgNuPPpHSgaBTYWex6A:Itb20pkaCqT5TBWgNQ7aVSx6A
Malware Config
Extracted
xtremerat
ellol.publicvm.com
Signatures
-
Detect XtremeRAT payload 6 IoCs
resource yara_rule behavioral2/memory/60-136-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/60-137-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4512-138-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4512-139-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/60-140-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4512-141-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/60-133-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/60-135-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/60-136-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/60-137-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4512-139-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/60-140-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4512-141-0x0000000010000000-0x000000001004D000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3112 set thread context of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 2 IoCs
pid pid_target Process procid_target 4556 4512 WerFault.exe 86 4596 4512 WerFault.exe 86 -
Suspicious use of FindShellTrayWindow 10 IoCs
pid Process 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe -
Suspicious use of SendNotifyMessage 10 IoCs
pid Process 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe -
Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 3112 wrote to memory of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 PID 3112 wrote to memory of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 PID 3112 wrote to memory of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 PID 3112 wrote to memory of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 PID 3112 wrote to memory of 60 3112 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 85 PID 60 wrote to memory of 4512 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 86 PID 60 wrote to memory of 4512 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 86 PID 60 wrote to memory of 4512 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 86 PID 60 wrote to memory of 4512 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 86 PID 60 wrote to memory of 3460 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 87 PID 60 wrote to memory of 3460 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 87 PID 60 wrote to memory of 3460 60 a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe"C:\Users\Admin\AppData\Local\Temp\a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of FindShellTrayWindow
- Suspicious use of SendNotifyMessage
- Suspicious use of WriteProcessMemory
PID:3112 -
C:\Users\Admin\AppData\Local\Temp\a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe"C:\Users\Admin\AppData\Local\Temp\a259696d00cced401546ad7a5853888225b5eb39697984241b5a9f9c52367cd5.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:60 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4512
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4512 -s 4884⤵
- Program crash
PID:4556
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4512 -s 4964⤵
- Program crash
PID:4596
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:3460
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 4512 -ip 45121⤵PID:1680
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 472 -p 4512 -ip 45121⤵PID:4328