Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
149s -
max time network
164s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
04/12/2022, 08:15
Static task
static1
Behavioral task
behavioral1
Sample
c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe
Resource
win10v2004-20220812-en
General
-
Target
c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe
-
Size
800KB
-
MD5
da7a7f0674855d40b5f32749a3292151
-
SHA1
492663f7c8f04c6678beec06797a39442182745e
-
SHA256
c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe
-
SHA512
4af5840283d8c90f5ce17035e3c3ef01d8889ed277eae96a39b76b5ea4750f68d0e50b6fda21cb12c92161ebcd775984f0c6766e9441bbcafded80e0793b7f23
-
SSDEEP
3072:vRAR2BY1emF6DA00EiqtTG142maYmOEenOBnZn/d4BVFPMuaNOi/mE5g4Sj01xS4:xKQSR
Malware Config
Extracted
xtremerat
zainee.no-ip.biz
Signatures
-
Detect XtremeRAT payload 7 IoCs
resource yara_rule behavioral2/memory/4736-134-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4736-136-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4736-135-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4736-137-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4268-138-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4736-139-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4268-140-0x0000000010000000-0x000000001004A000-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
description pid Process procid_target PID 4840 set thread context of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 -
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 1368 4268 WerFault.exe 81 4180 4268 WerFault.exe 81 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe -
Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4840 wrote to memory of 4736 4840 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 80 PID 4736 wrote to memory of 4268 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 81 PID 4736 wrote to memory of 4268 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 81 PID 4736 wrote to memory of 4268 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 81 PID 4736 wrote to memory of 4268 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 81 PID 4736 wrote to memory of 5104 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 82 PID 4736 wrote to memory of 5104 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 82 PID 4736 wrote to memory of 5104 4736 c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe"C:\Users\Admin\AppData\Local\Temp\c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4840 -
C:\Users\Admin\AppData\Local\Temp\c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe"C:\Users\Admin\AppData\Local\Temp\c6c4bc4f0b1823022d87d608e7f7f19e89d7737707b9e55d0c705fc455504bbe.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:4736 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4268
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4268 -s 4804⤵
- Program crash
PID:1368
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4268 -s 4884⤵
- Program crash
PID:4180
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:5104
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 464 -p 4268 -ip 42681⤵PID:5080
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 4268 -ip 42681⤵PID:4172