Analysis
- max time kernel
147s - max time network
153s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
04/03/2024, 00:41
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
b0cc1d172b96d8578830df6e94664ae6.exe
Resource
win7-20240221-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
b0cc1d172b96d8578830df6e94664ae6.exe
Resource
win10v2004-20240226-en
8 signatures
150 seconds
General
- Target b0cc1d172b96d8578830df6e94664ae6.exe
- Size 168KB
- Sample240304-a14a2sdh35
- SHA256 00c68867803ca8dacf7dd34c71cc52af6233513ea2ff5008da00fa5f2328381f
- MD5 b0cc1d172b96d8578830df6e94664ae6
- SHA1 733393fcaf348c56c42f527db3e4ce9dfa1855bd
- SHA512 071c46c4b98a37cec5f866d43f73c12f53edc86a5c4649bee96cb9dd0b121aa79f2b0fd81f26ad06546c2bf419722a58ebb705644fe4876734e06e6d300a6159
- SSDEEP 3072:/cY2MnUstI5Ag7O40TqzMwvmjw5emJYSu+RvNgCaveFq1NX+h3Zd:/v2mt+/7OdThwus5emGSnFeNXwD
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Signatures
- Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/1632-5-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1632-6-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4776-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/1632-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4776-9-0x0000000010000000-0x000000001004D000-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/1632-2-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1632-4-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1632-5-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1632-6-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4776-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/1632-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4776-9-0x0000000010000000-0x000000001004D000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1804 set thread context of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
- Program crash 2 IoCs
pid pid_target Process procid_target 208 4776 WerFault.exe 91 3884 4776 WerFault.exe 91 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1804 b0cc1d172b96d8578830df6e94664ae6.exe - Suspicious use of WriteProcessMemory 16 IoCs
description pid Process procid_target PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1804 wrote to memory of 1632 1804 b0cc1d172b96d8578830df6e94664ae6.exe 88 PID 1632 wrote to memory of 4776 1632 b0cc1d172b96d8578830df6e94664ae6.exe 91 PID 1632 wrote to memory of 4776 1632 b0cc1d172b96d8578830df6e94664ae6.exe 91 PID 1632 wrote to memory of 4776 1632 b0cc1d172b96d8578830df6e94664ae6.exe 91 PID 1632 wrote to memory of 4776 1632 b0cc1d172b96d8578830df6e94664ae6.exe 91 PID 1632 wrote to memory of 2488 1632 b0cc1d172b96d8578830df6e94664ae6.exe 92 PID 1632 wrote to memory of 2488 1632 b0cc1d172b96d8578830df6e94664ae6.exe 92 PID 1632 wrote to memory of 2488 1632 b0cc1d172b96d8578830df6e94664ae6.exe 92
Processes
-
C:\Users\Admin\AppData\Local\Temp\b0cc1d172b96d8578830df6e94664ae6.exe"C:\Users\Admin\AppData\Local\Temp\b0cc1d172b96d8578830df6e94664ae6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1804 -
C:\Users\Admin\AppData\Local\Temp\b0cc1d172b96d8578830df6e94664ae6.exeC:\Users\Admin\AppData\Local\Temp\b0cc1d172b96d8578830df6e94664ae6.exe2⤵
- Suspicious use of WriteProcessMemory
PID:1632 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4776
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4776 -s 4884⤵
- Program crash
PID:208
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4776 -s 4964⤵
- Program crash
PID:3884
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:2488
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 180 -p 4776 -ip 47761⤵PID:2696
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 556 -p 4776 -ip 47761⤵PID:1808