Analysis
-
max time kernel
133s -
max time network
155s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
06/12/2022, 10:25
Static task
static1
Behavioral task
behavioral1
Sample
bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe
Resource
win10v2004-20220812-en
General
-
Target
bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe
-
Size
867KB
-
MD5
30f5113831c2542dc3324b5c572512d6
-
SHA1
2052e361bd3462a41b5ba59b4f5a968b2bff1510
-
SHA256
bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b
-
SHA512
91ca7129e3d999765827d588e3f5417333985ff122d3b541e88a2e7850ec33d89bc414e5b0803e5361f8332e3170646b49931b701c156feb719ee3a5b9938684
-
SSDEEP
24576:kIabetnNvsBN7c49W1MNY5+XkAiAD4xd44MIgRhxYeoHvh7:Ab4nNvcNgD1MNY5+XkAiAD4xd44MIgRE
Malware Config
Extracted
xtremerat
nerozhack.ddns.com.br
alonedevil.no-ip.org
gameszero.dyndns.org
Signatures
-
Detect XtremeRAT payload 9 IoCs
resource yara_rule behavioral2/memory/392-139-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/392-140-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/392-141-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/392-143-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2056-144-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/3304-145-0x0000000000000000-mapping.dmp family_xtremerat behavioral2/memory/392-146-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/2056-147-0x0000000010000000-0x000000001004A000-memory.dmp family_xtremerat behavioral2/memory/3304-148-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.
-
Drops file in Drivers directory 2 IoCs
description ioc Process File opened for modification C:\Windows\system32\drivers\etc\System.exe taskmgr.exe File created C:\Windows\system32\drivers\etc\System.exe taskmgr.exe -
Adds Run key to start application 2 TTPs 4 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-2629973501-4017243118-3254762364-1000\Software\Microsoft\Windows\CurrentVersion\Run taskmgr.exe Set value (str) \REGISTRY\USER\S-1-5-21-2629973501-4017243118-3254762364-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\PlusServices = "C:\\Windows\\system32\\drivers\\etc\\System.exe" taskmgr.exe Key created \REGISTRY\MACHINE\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run taskmgr.exe Set value (str) \REGISTRY\MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run\UpdaterStartupUtility = "C:\\Windows\\system32\\drivers\\etc\\System.exe" taskmgr.exe -
AutoIT Executable 1 IoCs
AutoIT scripts compiled to PE executables.
resource yara_rule behavioral2/memory/4420-132-0x0000000000400000-0x00000000004BF000-memory.dmp autoit_exe -
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 4420 set thread context of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 1448 set thread context of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Program crash 4 IoCs
pid pid_target Process procid_target 2712 2056 WerFault.exe 81 4988 2056 WerFault.exe 81 4960 3304 WerFault.exe 82 4972 3304 WerFault.exe 82 -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 3304 taskmgr.exe -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 4420 wrote to memory of 1448 4420 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 79 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 1448 wrote to memory of 392 1448 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 80 PID 392 wrote to memory of 2056 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 81 PID 392 wrote to memory of 2056 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 81 PID 392 wrote to memory of 2056 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 81 PID 392 wrote to memory of 2056 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 81 PID 392 wrote to memory of 3304 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 82 PID 392 wrote to memory of 3304 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 82 PID 392 wrote to memory of 3304 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 82 PID 392 wrote to memory of 3304 392 bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe"C:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4420 -
C:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe"C:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1448 -
C:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exeC:\Users\Admin\AppData\Local\Temp\bc52fef0663fd4e3ce1b7e67284bc941d98e4d2e376f92231039398442651a8b.exe3⤵
- Suspicious use of WriteProcessMemory
PID:392 -
C:\Windows\SysWOW64\svchost.exesvchost.exe4⤵PID:2056
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2056 -s 4925⤵
- Program crash
PID:2712
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2056 -s 5085⤵
- Program crash
PID:4988
-
-
-
C:\WINDOWS\SysWOW64\taskmgr.exeC:\WINDOWS\system32\taskmgr.exe4⤵
- Drops file in Drivers directory
- Adds Run key to start application
- Suspicious use of SetWindowsHookEx
PID:3304 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3304 -s 10765⤵
- Program crash
PID:4960
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3304 -s 11005⤵
- Program crash
PID:4972
-
-
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 2056 -ip 20561⤵PID:3100
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 540 -p 2056 -ip 20561⤵PID:5072
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 544 -p 3304 -ip 33041⤵PID:5004
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 568 -p 3304 -ip 33041⤵PID:5044