Analysis
- max time kernel
90s - max time network
93s - platform
windows11-21h2_x64 - resource
win11-20240419-en - resource tags
arch:x64arch:x86image:win11-20240419-enlocale:en-usos:windows11-21h2-x64system - submitted
29/06/2024, 04:02
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe
Resource
win10v2004-20240611-en
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe
Resource
win11-20240419-en
3 signatures
150 seconds
General
- Target 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe
- Size 520KB
- Sample240629-el1c3azgrf
- SHA256 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3
- MD5 3900de86228c8f839d6d4b483794457b
- SHA1 90e24676fd3ebcda8635704e762e83d3fbd9cfba
- SHA512 5bd0c7f623a6a3c11091391c72868c4462525618164d40a28a19dc5913766b7ebb2878206b4077a7374de23562343748e27e4594ad5c56434fb9fff40e91f4dc
- SSDEEP 12288:EnlK6zDfP9TWIBmoWUlANmKr1AAMiBPM1:ErPf1CIUYJKrrPM
- MD5 SHA1 SHA512 SSDEEP
Score
5/10
Malware Config
Signatures
- Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3872 set thread context of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 - Program crash 1 IoCs
pid pid_target Process procid_target 2512 3872 WerFault.exe 75 - Suspicious use of WriteProcessMemory 15 IoCs
description pid Process procid_target PID 3872 wrote to memory of 2564 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 77 PID 3872 wrote to memory of 2564 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 77 PID 3872 wrote to memory of 2564 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 77 PID 3872 wrote to memory of 4836 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 78 PID 3872 wrote to memory of 4836 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 78 PID 3872 wrote to memory of 4836 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 78 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79 PID 3872 wrote to memory of 3492 3872 00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe 79
Processes
-
C:\Users\Admin\AppData\Local\Temp\00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe"C:\Users\Admin\AppData\Local\Temp\00c4e525ffb64ff858bb8922e3ab46ee6d65c67a3fa7d9f3a614aaf1604f27e3.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3872 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2564
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4836
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3492
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3872 -s 3602⤵
- Program crash
PID:2512
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 3872 -ip 38721⤵PID:2628