Analysis
-
max time kernel
118s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13-10-2023 04:58
Static task
static1
Behavioral task
behavioral1
Sample
a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe
Resource
win10v2004-20230915-en
General
-
Target
a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe
-
Size
1.4MB
-
MD5
88c95838fde0cb4cfc598e5ae82bef94
-
SHA1
b16d7b965209eb06e326684546357bca22540590
-
SHA256
a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869
-
SHA512
ffe99c5d10e45f8e3925c21e06c0aa5e4ef43868df84b7a98fbed2314f0e7ad824deb66ff56db6b051c20a04ec83657d147bbe1179eeb56559724fa7587bd68a
-
SSDEEP
24576:64PTAUYmOIDmqtiqdv47lyJR7DapuSiCn+VXRLkiX5cdrDrrgy60G:vPTAOagjv2+g+QucdrDrtG
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2688 set thread context of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 -
Program crash 1 IoCs
pid pid_target Process procid_target 936 2752 WerFault.exe 31 -
Suspicious use of WriteProcessMemory 35 IoCs
description pid Process procid_target PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2332 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 29 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2732 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 30 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2688 wrote to memory of 2752 2688 a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe 31 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32 PID 2752 wrote to memory of 936 2752 AppLaunch.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe"C:\Users\Admin\AppData\Local\Temp\a1d6738dae79ebd8a13c87a814f86fc05f00cc89cc9ba8dbd82ba0e7254b0869.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2688 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2332
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2732
-
-
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:2752 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2752 -s 2003⤵
- Program crash
PID:936
-
-