Analysis
-
max time kernel
122s -
max time network
138s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 22:48
Static task
static1
Behavioral task
behavioral1
Sample
206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe
Resource
win10v2004-20230915-en
General
-
Target
206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe
-
Size
1.4MB
-
MD5
26d2bdb96ec12bc5365bea79b5193a92
-
SHA1
9df12cec889ddb87cbcc4440743f7954925639de
-
SHA256
206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50
-
SHA512
7df7d3d04dca04b923ee9b4f9ad2b023735bb7e90bc8aec8adcfeb7f054b2f912f7af3d02992c3656b8ab756bc4c0e42c8029ee7c18472425e032f29156a847b
-
SSDEEP
24576:lzxSd8DMSCi0QgCyPyegrkjM6BNu0gw8+LlxnYINltAdDQcRBv8ozUXYf:jSd8Dd0jydrkjhuZwFfnYIBUDQcLv8Wh
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3048 set thread context of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 -
Program crash 2 IoCs
pid pid_target Process procid_target 2348 3048 WerFault.exe 4 3068 1060 WerFault.exe 31 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 1060 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 31 PID 3048 wrote to memory of 2348 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 32 PID 3048 wrote to memory of 2348 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 32 PID 3048 wrote to memory of 2348 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 32 PID 3048 wrote to memory of 2348 3048 206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe 32 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33 PID 1060 wrote to memory of 3068 1060 AppLaunch.exe 33
Processes
-
C:\Users\Admin\AppData\Local\Temp\206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe"C:\Users\Admin\AppData\Local\Temp\206642eb2f40851e1e9b035c7ce869b83dadec13ed42872dd693a28448fb3c50_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3048 -
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:1060 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1060 -s 2003⤵
- Program crash
PID:3068
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3048 -s 922⤵
- Program crash
PID:2348
-