Analysis
-
max time kernel
9s -
max time network
3s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
12-10-2022 14:36
Static task
static1
Behavioral task
behavioral1
Sample
3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe
Resource
win10v2004-20220812-en
General
-
Target
3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe
-
Size
134KB
-
MD5
697fb9485469007d6e4c31b72265bc90
-
SHA1
d2a37c56f97ffeaf5b34ccd43ceb53463fc21eb5
-
SHA256
3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e
-
SHA512
2ba8fc34512bfbe4a879cee494f37c19b63eea6ab3e11ce51a66304d64309e33e5ee2f117783b746d731663ed1b3f6d52852eb7f0d9524c2bdfbeb29e9430cb7
-
SSDEEP
3072:W4ofSu5F16DVWaMyKxgUEkUbQI4ng4vST:8Su5n6DVWaExfI4OT
Malware Config
Extracted
xtremerat
ahmed1111.no-ip.biz
Signatures
-
Detect XtremeRAT payload 6 IoCs
resource yara_rule behavioral2/memory/1728-138-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/1728-139-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/4216-140-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/4216-141-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/1728-142-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/4216-143-0x0000000010000000-0x0000000010048000-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/1728-135-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1728-137-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1728-138-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1728-139-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/4216-141-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1728-142-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/4216-143-0x0000000010000000-0x0000000010048000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2876 set thread context of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 -
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 2156 4216 WerFault.exe 78 4708 4216 WerFault.exe 78 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe -
Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 2876 wrote to memory of 1728 2876 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 77 PID 1728 wrote to memory of 4216 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 78 PID 1728 wrote to memory of 4216 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 78 PID 1728 wrote to memory of 4216 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 78 PID 1728 wrote to memory of 4216 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 78 PID 1728 wrote to memory of 4848 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 79 PID 1728 wrote to memory of 4848 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 79 PID 1728 wrote to memory of 4848 1728 3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe"C:\Users\Admin\AppData\Local\Temp\3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2876 -
C:\Users\Admin\AppData\Local\Temp\3dd55aaa3bd6ff4db89ba236b3d2eb97676f402a494421269a627ecb5e20b76e.exe
- Suspicious use of WriteProcessMemory
PID:1728 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4216
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4216 -s 4804⤵
- Program crash
PID:2156
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4216 -s 4884⤵
- Program crash
PID:4708
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4848
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4216 -ip 42161⤵PID:900
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 4216 -ip 42161⤵PID:3576