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
16/03/2024, 00:59
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe
Resource
win7-20240221-en
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe
Resource
win10v2004-20240226-en
5 signatures
150 seconds
General
- Target ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe
- Size 179KB
- Sample240316-bcg9cahe93
- SHA256 a7fe53e2629166df60a788748ed6c9426c4e42577821fc91482d4b0769103d22
- MD5 ccb3c9ebc1d37fbaa3cf7b932f27bf4b
- SHA1 71fc70886ea95d9f8baa1357a6029854784c6954
- SHA512 881ff89a02cbc285b012cac68c452b9d346d466482b1e1c1e2c5cf623322553647c8f32d85ac5b50bdf5f17992d3cc82651db268a2a30c9ab04e598d6747eb6c
- SSDEEP 3072:51ccv/oXBcT7JkjkstZ1uy/Z17mko9C0mRY9AGFZC8miUYX:51cpxcx8J5uybal9CxRY9AGroiU4
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
xtremerat
C2
-
esam2at.no-ip.biz
Signatures
- Detect XtremeRAT payload 4 IoCs
resource yara_rule behavioral2/memory/180-9-0x0000000010000000-0x0000000010055000-memory.dmp family_xtremerat behavioral2/memory/1752-10-0x0000000010000000-0x0000000010055000-memory.dmp family_xtremerat behavioral2/memory/180-11-0x0000000010000000-0x0000000010055000-memory.dmp family_xtremerat behavioral2/memory/1752-13-0x0000000010000000-0x0000000010055000-memory.dmp family_xtremerat - XtremeRAT
The XtremeRAT was developed by xtremecoder and has been available since at least 2010, and written in Delphi.
- 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 1260 1752 WerFault.exe 86 2012 1752 WerFault.exe 86 - Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 180 wrote to memory of 1752 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 86 PID 180 wrote to memory of 1752 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 86 PID 180 wrote to memory of 1752 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 86 PID 180 wrote to memory of 1752 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 86 PID 180 wrote to memory of 3960 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 87 PID 180 wrote to memory of 3960 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 87 PID 180 wrote to memory of 3960 180 ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe 87
Processes
-
C:\Users\Admin\AppData\Local\Temp\ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe"C:\Users\Admin\AppData\Local\Temp\ccb3c9ebc1d37fbaa3cf7b932f27bf4b.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:180 -
C:\Windows\SysWOW64\svchost.exesvchost.exe2⤵PID:1752
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1752 -s 4843⤵
- Program crash
PID:1260
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1752 -s 5043⤵
- Program crash
PID:2012
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"2⤵PID:3960
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 1752 -ip 17521⤵PID:2000
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 524 -p 1752 -ip 17521⤵PID:436