Analysis
-
max time kernel
117s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20240903-en -
resource tags
arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system -
submitted
17-09-2024 01:35
Static task
static1
Behavioral task
behavioral1
Sample
d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe
Resource
win7-20240903-en
Behavioral task
behavioral2
Sample
d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe
Resource
win10v2004-20240802-en
General
-
Target
d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe
-
Size
135KB
-
MD5
458d31ecc5a490d5bda8d52e7ca8a5b6
-
SHA1
213aac6538f2d98169f655d2252a13f50e6f31a5
-
SHA256
d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50
-
SHA512
a3dfdf74773a7f195e26e4225f79394664d808777f50cbadc4571e36b55aab8c4c6864fbc02ab83378aa1904a403ef2915c98585d541f0babb324b28bf56bb2b
-
SSDEEP
3072:f5zF1UvqLHTCCrSIpnwF8vIzKJjGjssSDrI8pSQbAAmVBVa5GKYzEO:71zLN+WvnHsSv1zJmV2SEO
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2700 set thread context of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 -
Program crash 1 IoCs
pid pid_target Process procid_target 2732 2680 WerFault.exe 34 -
System Location Discovery: System Language Discovery 1 TTPs 2 IoCs
Attempt gather information about the system language of a victim in order to infer the geographical location of that host.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language RegAsm.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2728 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 32 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2696 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 33 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2700 wrote to memory of 2680 2700 d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe 34 PID 2680 wrote to memory of 2732 2680 RegAsm.exe 35 PID 2680 wrote to memory of 2732 2680 RegAsm.exe 35 PID 2680 wrote to memory of 2732 2680 RegAsm.exe 35 PID 2680 wrote to memory of 2732 2680 RegAsm.exe 35
Processes
-
C:\Users\Admin\AppData\Local\Temp\d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe"C:\Users\Admin\AppData\Local\Temp\d574de9b5d8f74451207c6b4f2b6f63e1b58f8d8f50dc03a722638c866a41f50.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2700 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2728
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2696
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2680 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2680 -s 2523⤵
- Program crash
PID:2732
-
-