Analysis
- max time kernel
136s - max time network
148s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
11/03/2024, 17:33
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
c130e87efbe1c3f5d4006fbec95a2588.exe
Resource
win7-20240221-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
c130e87efbe1c3f5d4006fbec95a2588.exe
Resource
win10v2004-20240226-en
8 signatures
150 seconds
General
- Target c130e87efbe1c3f5d4006fbec95a2588.exe
- Size 225KB
- Sample240311-v5bf2she5x
- SHA256 0aba8635df1108abf042801f8f5cdb25c02405899c81441caf3be9cf1e47a4e7
- MD5 c130e87efbe1c3f5d4006fbec95a2588
- SHA1 80c7a16430a662d0db763048c3da51aeb2181ad1
- SHA512 de770b506f461a851f26a9bdedbd55d6c5aa4a650d8e99655d2e9f766832ff302e5624604d9bb2a2db775b661b21632dab1af7f3f281f33ff9c67daee8312f7d
- SSDEEP 3072:+mZlKlEzDq60vSgHbem3myQ8E09JVFyqTGbN5QvuS6nqx3s5/nTZxPcSCAppuBZ7:+1bTbykdf6YLd
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
xtremerat
C2
-
shakur2.dyndns.biz
Signatures
- Detect XtremeRAT payload 5 IoCs
resource yara_rule behavioral2/memory/4216-8-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4216-7-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4796-9-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4216-10-0x0000000010000000-0x000000001004D000-memory.dmp family_xtremerat behavioral2/memory/4796-11-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/4216-4-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4216-6-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4216-8-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4216-7-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4796-9-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4216-10-0x0000000010000000-0x000000001004D000-memory.dmp upx behavioral2/memory/4796-11-0x0000000010000000-0x000000001004D000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4248 set thread context of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 - 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 2916 4796 WerFault.exe 99 3904 4796 WerFault.exe 99 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4248 c130e87efbe1c3f5d4006fbec95a2588.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4248 wrote to memory of 4216 4248 c130e87efbe1c3f5d4006fbec95a2588.exe 98 PID 4216 wrote to memory of 4796 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 99 PID 4216 wrote to memory of 4796 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 99 PID 4216 wrote to memory of 4796 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 99 PID 4216 wrote to memory of 4796 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 99 PID 4216 wrote to memory of 4632 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 100 PID 4216 wrote to memory of 4632 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 100 PID 4216 wrote to memory of 4632 4216 c130e87efbe1c3f5d4006fbec95a2588.exe 100
Processes
-
C:\Users\Admin\AppData\Local\Temp\c130e87efbe1c3f5d4006fbec95a2588.exe"C:\Users\Admin\AppData\Local\Temp\c130e87efbe1c3f5d4006fbec95a2588.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4248 -
C:\Users\Admin\AppData\Local\Temp\c130e87efbe1c3f5d4006fbec95a2588.exe"C:\Users\Admin\AppData\Local\Temp\c130e87efbe1c3f5d4006fbec95a2588.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:4216 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:4796
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4796 -s 4804⤵
- Program crash
PID:2916
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4796 -s 5044⤵
- Program crash
PID:3904
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:4632
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4796 -ip 47961⤵PID:4892
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 520 -p 4796 -ip 47961⤵PID:4612
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4092 --field-trial-handle=2276,i,11674642242468042059,14711253743544118298,262144 --variations-seed-version /prefetch:81⤵PID:4692