Analysis
-
max time kernel
118s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20231023-en -
resource tags
arch:x64arch:x86image:win7-20231023-enlocale:en-usos:windows7-x64system -
submitted
13/11/2023, 11:22
Static task
static1
Behavioral task
behavioral1
Sample
5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe
Resource
win7-20231023-en
Behavioral task
behavioral2
Sample
5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe
Resource
win10v2004-20231023-en
General
-
Target
5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe
-
Size
752KB
-
MD5
b59db05dcd3bc148f213915dcd25ebee
-
SHA1
76ee3c38bbd040f09596108cd5fa5df4f54be58e
-
SHA256
5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f
-
SHA512
1fbf808b44829426cb224e793bf1981d402bd468fa93462dbe84e39b1145c20c9347fa4228fdbe366f816765d83b9b7d14d40c10bd470b4a946e2e9b4581fe79
-
SSDEEP
12288:WWOTNXc3VGunBAFnS5+4cW/8A/kBEs39bbPwpbgQ2Jhr+ghANSSTf:53suBqS5v/0AaEstHoglR+gqS6
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2028 set thread context of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 1816 2640 WerFault.exe 28 -
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 2640 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2028 wrote to memory of 2640 2028 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 28 PID 2640 wrote to memory of 1816 2640 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 29 PID 2640 wrote to memory of 1816 2640 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 29 PID 2640 wrote to memory of 1816 2640 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 29 PID 2640 wrote to memory of 1816 2640 5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe"C:\Users\Admin\AppData\Local\Temp\5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2028 -
C:\Users\Admin\AppData\Local\Temp\5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe"C:\Users\Admin\AppData\Local\Temp\5fbe64657d05cbbba18f255662e902d7b519e6b1eca0610a518c4031f828130f.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:2640 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2640 -s 363⤵
- Program crash
PID:1816
-
-