Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
84s -
max time network
148s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
02/10/2022, 06:40
Static task
static1
Behavioral task
behavioral1
Sample
30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe
Resource
win10v2004-20220812-en
General
-
Target
30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe
-
Size
348KB
-
MD5
63d9892830af795b8ef5886548597240
-
SHA1
4ed69df13436b0976ff3a52909e18ff109e66a1f
-
SHA256
30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79
-
SHA512
2d9a0270e171fd9040e6c51e7da769de09e28570462a987ed66017a311902a9f80d37f3fbb1d466eb6c89c737b3c1e7e55a9d2afce60dc5339f1465c6ab1185d
-
SSDEEP
6144:F7OFdDwI4ZMSiHGMbTfH5v05Ap42ZbR0LAhQ+nTLz5BylgYXQUeFUzoE6LVbXV+V:lS4ZHeB/906pNZuLQQ+9BymeKV9bl+ma
Malware Config
Signatures
-
Detect XtremeRAT payload 7 IoCs
resource yara_rule behavioral2/memory/4816-143-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4816-144-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4816-145-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4816-146-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4584-147-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4816-148-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4584-149-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 2 IoCs
description pid Process procid_target PID 2184 set thread context of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 4708 set thread context of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.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 3444 4584 WerFault.exe 83 3400 4584 WerFault.exe 83 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 2184 wrote to memory of 4708 2184 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 81 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4708 wrote to memory of 4816 4708 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 82 PID 4816 wrote to memory of 4584 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 83 PID 4816 wrote to memory of 4584 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 83 PID 4816 wrote to memory of 4584 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 83 PID 4816 wrote to memory of 4584 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 83 PID 4816 wrote to memory of 3504 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 84 PID 4816 wrote to memory of 3504 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 84 PID 4816 wrote to memory of 3504 4816 30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe"C:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2184 -
C:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exeC:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4708 -
C:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe"C:\Users\Admin\AppData\Local\Temp\30c0983f9d2e0c185bbfc2d91737db5d6cc409bdfd3ec70c767e1fec5b7b6d79.exe"3⤵
- Suspicious use of WriteProcessMemory
PID:4816 -
C:\Windows\SysWOW64\svchost.exesvchost.exe4⤵PID:4584
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4584 -s 4885⤵
- Program crash
PID:3444
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4584 -s 5045⤵
- Program crash
PID:3400
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"4⤵PID:3504
-
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4584 -ip 45841⤵PID:2608
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 536 -p 4584 -ip 45841⤵PID:4760