Analysis
- max time kernel
149s - max time network
151s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
13/03/2024, 07:38
Behavioral task
behavioral1
Sample
c555549a357334ca22ddefcb3383c75b.exe
Resource
win7-20240220-en
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
c555549a357334ca22ddefcb3383c75b.exe
Resource
win10v2004-20240226-en
6 signatures
150 seconds
General
- Target c555549a357334ca22ddefcb3383c75b.exe
- Size 33KB
- Sample240313-jgt3psga3v
- SHA256 e0465698dcd24adc8207fa95c10c06c2a01905b75d31c06e648038ff857a82dd
- MD5 c555549a357334ca22ddefcb3383c75b
- SHA1 02ef0686bbb6dba027e0deae6989bd0b91549571
- SHA512 04460cda14d2e3d53eb4c85f81f5a6c934f9b3e10fa987b6d2f277a0e7a3c6de6d78ab3ffce0f55828849d42a0b0fd0d60d003e812e9a10b37d1d15401e703df
- SSDEEP 768:VMuijtHf5g7/IIG3bGcYDBSvFIWuePQDGEsgCBaXv+DzA:eNW71rcYDAWeoDrsDYQ
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Signatures
- Detect XtremeRAT payload 3 IoCs
resource yara_rule behavioral2/memory/3740-1-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/212-2-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/3740-3-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/212-0-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3740-1-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/212-2-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/3740-3-0x0000000010000000-0x000000001004D000-memory.dmp upx - 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 400 3740 WerFault.exe 89 5052 3740 WerFault.exe 89 - Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 212 wrote to memory of 3740 212 c555549a357334ca22ddefcb3383c75b.exe 89 PID 212 wrote to memory of 3740 212 c555549a357334ca22ddefcb3383c75b.exe 89 PID 212 wrote to memory of 3740 212 c555549a357334ca22ddefcb3383c75b.exe 89 PID 212 wrote to memory of 3740 212 c555549a357334ca22ddefcb3383c75b.exe 89 PID 212 wrote to memory of 4392 212 c555549a357334ca22ddefcb3383c75b.exe 90 PID 212 wrote to memory of 4392 212 c555549a357334ca22ddefcb3383c75b.exe 90 PID 212 wrote to memory of 4392 212 c555549a357334ca22ddefcb3383c75b.exe 90
Processes
-
C:\Users\Admin\AppData\Local\Temp\c555549a357334ca22ddefcb3383c75b.exe"C:\Users\Admin\AppData\Local\Temp\c555549a357334ca22ddefcb3383c75b.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:212 -
C:\Windows\SysWOW64\svchost.exesvchost.exe2⤵PID:3740
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3740 -s 4723⤵
- Program crash
PID:400
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3740 -s 4883⤵
- Program crash
PID:5052
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"2⤵PID:4392
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3740 -ip 37401⤵PID:5076
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 492 -p 3740 -ip 37401⤵PID:3988