Analysis
- max time kernel
145s - max time network
157s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
20/03/2024, 00:12
Behavioral task
behavioral1
Sample
d76cf28650d7b53ec35e1857f87ab56a.exe
Resource
win7-20240319-en
7 signatures
150 seconds
Behavioral task
behavioral2
Sample
d76cf28650d7b53ec35e1857f87ab56a.exe
Resource
win10v2004-20240226-en
8 signatures
150 seconds
General
- Target d76cf28650d7b53ec35e1857f87ab56a.exe
- Size 107KB
- Sample240320-ag6basbe47
- SHA256 00317c86477f4e78a177b3e737ab1ec4e9e1502d1f111c154b400be39528fe1e
- MD5 d76cf28650d7b53ec35e1857f87ab56a
- SHA1 960e49692fc89b3c350f0b855c8fd33894974869
- SHA512 336e9accd121953337fe177277160c38d942f6382b0e4501b47547be14c82cbe408b7eb050f73a8f94fc70e40cbdcc0dadd7bbc3a4a4d53f04d747283014764e
- SSDEEP 3072:7YdWJEuiXU96b1Y0H/CDEJS+c9yEsntkEm:7YSiv1Y0H6DEJS+c9yEY0
- MD5 SHA1 SHA512 SSDEEP
Score
10/10
Malware Config
Extracted
Family
-
xtremerat
C2
-
ahmed1111.no-ip.biz
Signatures
- Detect XtremeRAT payload 4 IoCs
resource yara_rule behavioral2/memory/1284-10-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3368-11-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/1284-12-0x0000000010000000-0x0000000010048000-memory.dmp family_xtremerat behavioral2/memory/3368-13-0x0000000010000000-0x0000000010048000-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/392-0-0x0000000000400000-0x00000000004E3000-memory.dmp upx behavioral2/memory/392-1-0x0000000000400000-0x00000000004E3000-memory.dmp upx behavioral2/memory/392-2-0x0000000000400000-0x00000000004E3000-memory.dmp upx behavioral2/memory/1284-6-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1284-8-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/392-9-0x0000000000400000-0x00000000004E3000-memory.dmp upx behavioral2/memory/1284-10-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/3368-11-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/1284-12-0x0000000010000000-0x0000000010048000-memory.dmp upx behavioral2/memory/3368-13-0x0000000010000000-0x0000000010048000-memory.dmp upx - Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 392 set thread context of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 - 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 3756 3368 WerFault.exe 91 524 3368 WerFault.exe 91 - Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 392 d76cf28650d7b53ec35e1857f87ab56a.exe - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 392 wrote to memory of 1284 392 d76cf28650d7b53ec35e1857f87ab56a.exe 89 PID 1284 wrote to memory of 3368 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 91 PID 1284 wrote to memory of 3368 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 91 PID 1284 wrote to memory of 3368 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 91 PID 1284 wrote to memory of 3368 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 91 PID 1284 wrote to memory of 1008 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 92 PID 1284 wrote to memory of 1008 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 92 PID 1284 wrote to memory of 1008 1284 d76cf28650d7b53ec35e1857f87ab56a.exe 92
Processes
-
C:\Users\Admin\AppData\Local\Temp\d76cf28650d7b53ec35e1857f87ab56a.exe"C:\Users\Admin\AppData\Local\Temp\d76cf28650d7b53ec35e1857f87ab56a.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:392 -
C:\Users\Admin\AppData\Local\Temp\d76cf28650d7b53ec35e1857f87ab56a.exe"C:\Users\Admin\AppData\Local\Temp\d76cf28650d7b53ec35e1857f87ab56a.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1284 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵PID:3368
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3368 -s 4924⤵
- Program crash
PID:3756
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3368 -s 5124⤵
- Program crash
PID:524
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"3⤵PID:1008
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 184 -p 3368 -ip 33681⤵PID:4440
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 512 -p 3368 -ip 33681⤵PID:3296