Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
51s -
max time network
51s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
19/06/2024, 17:23
Static task
static1
Behavioral task
behavioral1
Sample
fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe
Resource
win10v2004-20240508-en
Behavioral task
behavioral2
Sample
fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe
Resource
win11-20240508-en
General
-
Target
fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe
-
Size
525KB
-
MD5
555259d9ac1f9da27667485bfc3ab9af
-
SHA1
59d61d0aa693f28ba68b0de8fd3b11dc206b76c4
-
SHA256
fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede
-
SHA512
ee1e2b3ca43eff5384298c251f1f0b6184a8a892410f998e40202dbc1376da45a1af3643fd5f490c3cd3f1f5fd420759a121c892f969e016d2c0daf11209e45b
-
SSDEEP
12288:4MLTuJtddskY7k1dyXbRQESs/mFKXuiPK0Lv:4zJth1IxQShPK0L
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1752 set thread context of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 -
Program crash 1 IoCs
pid pid_target Process procid_target 1364 1752 WerFault.exe 81 -
Suspicious use of WriteProcessMemory 12 IoCs
description pid Process procid_target PID 1752 wrote to memory of 3268 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 82 PID 1752 wrote to memory of 3268 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 82 PID 1752 wrote to memory of 3268 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 82 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83 PID 1752 wrote to memory of 4408 1752 fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe"C:\Users\Admin\AppData\Local\Temp\fa4491dbe5eb3d35c9f5884d746235769999d536d30033f4cf38633ce2343ede.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1752 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:3268
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:4408
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1752 -s 2802⤵
- Program crash
PID:1364
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 1752 -ip 17521⤵PID:2124