Analysis
-
max time kernel
141s -
max time network
154s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03/12/2022, 16:22
Static task
static1
Behavioral task
behavioral1
Sample
ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe
Resource
win10v2004-20220812-en
General
-
Target
ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe
-
Size
108KB
-
MD5
235b427faf680f993abc1942f180bbde
-
SHA1
f376d85034e732df4c27365a514972001b0b0474
-
SHA256
ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce
-
SHA512
42eb7a8879e144d93269431083b405cdfed45a0cde78f59675cf8e81b2b126b12395f7ed0d9511bef33f6c13e8b50d595a6e2ddf31be58b8d7ccc686c2ba409d
-
SSDEEP
1536:6YTx/EFizHrIksvsYEIwZGhB7H2X/QuPNPlqwAmLOqIxDh871vNNlzx:62LIFP7WX7lqw5OqCh6xp
Malware Config
Extracted
xtremerat
\Users\richard\AppData\Roaming\Microsoft\linep.no-ip.org
Signatures
-
Detect XtremeRAT payload 8 IoCs
resource yara_rule behavioral2/memory/5116-134-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/5116-135-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/5116-136-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/5116-137-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/5116-138-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4444-139-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/5116-140-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/4444-141-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 448 set thread context of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.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 3436 4444 WerFault.exe 80 2332 4444 WerFault.exe 80 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe -
Suspicious use of WriteProcessMemory 20 IoCs
description pid Process procid_target PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 448 wrote to memory of 5116 448 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 79 PID 5116 wrote to memory of 4444 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 80 PID 5116 wrote to memory of 4444 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 80 PID 5116 wrote to memory of 4444 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 80 PID 5116 wrote to memory of 4444 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 80 PID 5116 wrote to memory of 4904 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 81 PID 5116 wrote to memory of 4904 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 81 PID 5116 wrote to memory of 4904 5116 ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe 81
Processes
-
C:\Users\Admin\AppData\Local\Temp\ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe"C:\Users\Admin\AppData\Local\Temp\ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:448 -
C:\Users\Admin\AppData\Local\Temp\ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exeC:\Users\Admin\AppData\Local\Temp\ed19890e682b425e2e793e6d50d2007fbc972d99d1a59bdf84dac85efc5b56ce.exe2⤵
- Suspicious use of WriteProcessMemory
PID:5116 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4444
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4444 -s 4804⤵
- Program crash
PID:3436
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4444 -s 4884⤵
- Program crash
PID:2332
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4904
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 360 -p 4444 -ip 44441⤵PID:3388
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 4444 -ip 44441⤵PID:5112