Analysis
-
max time kernel
117s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 13:01
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe
Resource
win10v2004-20230915-en
windows10-2004-x64
3 signatures
150 seconds
General
-
Target
9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe
-
Size
391KB
-
MD5
a13a180ccdfa150f4a381f8489805f43
-
SHA1
84fdf30ee32a4ddf0f41cf6d5a61afc9cb41b958
-
SHA256
9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b
-
SHA512
eb2a18ae4f96741b0187afde03c828e298dbaaf889f1547366374d031fd0f8994fc03241deb903fb2affa666f037ba17429e09411aaecfbd282aad063fc5cadc
-
SSDEEP
12288:wboHsPCbwwq2Wg/qkFXQ+93BpuCTeYyUi:wboYC7k893BpurYf
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2736 set thread context of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2644 2736 WerFault.exe 27 2716 2524 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2524 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 29 PID 2736 wrote to memory of 2644 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 30 PID 2736 wrote to memory of 2644 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 30 PID 2736 wrote to memory of 2644 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 30 PID 2736 wrote to memory of 2644 2736 9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe 30 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31 PID 2524 wrote to memory of 2716 2524 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe"C:\Users\Admin\AppData\Local\Temp\9d0e1d8959e30aab2c34d57c91e48d7208cd92a8cee92d83613ce219cba0b59b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2736 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2524 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2524 -s 1963⤵
- Program crash
PID:2716
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2736 -s 922⤵
- Program crash
PID:2644
-