Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
94s -
max time network
156s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
05/12/2022, 12:28
Static task
static1
Behavioral task
behavioral1
Sample
919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe
Resource
win10v2004-20220901-en
General
-
Target
919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe
-
Size
537KB
-
MD5
8c9baa45fb37a6c89cb9861dcc8d2f1f
-
SHA1
65342cfdd656011df268269cfa07f93d351bca00
-
SHA256
919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3
-
SHA512
f76cfa6dab53abc804285780d52c4608a11b90461930ea03d11e2b3a58c89d67254f2b1e4f25adabc38156dab9aaaecc8298f8b2f9b4dddfa15fb5d8a0039f0b
-
SSDEEP
12288:UoS493ACIl7vI1kiqHNnyVek/a4QmHNX467p9KMSL8vbfcF3baixe/:UoIjIbgyLC495467zKMRzcVei4/
Malware Config
Extracted
xtremerat
maradona.no-ip.org
Signatures
-
Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/2160-141-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/5088-143-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/5088-144-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/2160-145-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/5088-146-0x0000000010000000-0x000000001004E000-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/2160-136-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2160-138-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2160-141-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2160-140-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/5088-144-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2160-145-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/5088-146-0x0000000010000000-0x000000001004E000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5060 set thread context of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 -
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 3524 5088 WerFault.exe 83 2772 5088 WerFault.exe 83 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 5060 wrote to memory of 2160 5060 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 82 PID 2160 wrote to memory of 5088 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 83 PID 2160 wrote to memory of 5088 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 83 PID 2160 wrote to memory of 5088 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 83 PID 2160 wrote to memory of 5088 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 83 PID 2160 wrote to memory of 3616 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 84 PID 2160 wrote to memory of 3616 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 84 PID 2160 wrote to memory of 3616 2160 919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe"C:\Users\Admin\AppData\Local\Temp\919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5060 -
C:\Users\Admin\AppData\Local\Temp\919b080c6200fbf05a741ec572f077b116d87849fa595d90daa6537e3f9cbaf3.exe
- Suspicious use of WriteProcessMemory
PID:2160 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:5088
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5088 -s 4804⤵
- Program crash
PID:3524
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5088 -s 4884⤵
- Program crash
PID:2772
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:3616
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 5088 -ip 50881⤵PID:2748
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 456 -p 5088 -ip 50881⤵PID:2292