Analysis
-
max time kernel
148s -
max time network
177s -
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, 02:33
Static task
static1
Behavioral task
behavioral1
Sample
f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe
Resource
win10v2004-20220812-en
General
-
Target
f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe
-
Size
1.4MB
-
MD5
739211836e07f77990d47bffd200b91e
-
SHA1
7eeb5122c832743a378f3adef78b337b11069cb3
-
SHA256
f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a
-
SHA512
6085147fb90d28cabde81baa571f5a81acdb24b02ea61477a78418319e491e21954e4e2c927ed54c6df3d774a7ac34b4a84aad01c64ad86c5b32ef1b1bc33214
-
SSDEEP
24576:+tkg5IKOsopEeMAMgiMWPtS3L65Jcr1lK13:vJKOsopZMAMkfW5ePK13
Malware Config
Extracted
xtremerat
xxtreme.no-ip.org
Signatures
-
Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/2564-145-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/1932-146-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/2564-147-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/1932-148-0x0000000010000000-0x000000001004E000-memory.dmp family_xtremerat behavioral2/memory/2564-149-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/2564-142-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2564-144-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2564-145-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2564-147-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/1932-148-0x0000000010000000-0x000000001004E000-memory.dmp upx behavioral2/memory/2564-149-0x0000000010000000-0x000000001004E000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5080 set thread context of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 -
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 4864 1932 WerFault.exe 80 4868 1932 WerFault.exe 80 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe -
Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 5080 wrote to memory of 2564 5080 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 79 PID 2564 wrote to memory of 1932 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 80 PID 2564 wrote to memory of 1932 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 80 PID 2564 wrote to memory of 1932 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 80 PID 2564 wrote to memory of 1932 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 80 PID 2564 wrote to memory of 4464 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 81 PID 2564 wrote to memory of 4464 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 81 PID 2564 wrote to memory of 4464 2564 f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe"C:\Users\Admin\AppData\Local\Temp\f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5080 -
C:\Users\Admin\AppData\Local\Temp\f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe"C:\Users\Admin\AppData\Local\Temp\f13fe25f6ca305b3f8064e8e31420909055157a2edab59f022324e82c34c8c9a.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2564 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:1932
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1932 -s 4804⤵
- Program crash
PID:4864
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1932 -s 4884⤵
- Program crash
PID:4868
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4464
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 188 -p 1932 -ip 19321⤵PID:4876
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 520 -p 1932 -ip 19321⤵PID:4800