c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8

Analysis

max time kernel
6s
max time network
34s
platform
windows7_x64
resource
win7-20221111-en
resource tags

arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system
submitted
02/12/2022, 00:24

Target

c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe
Size

184KB
MD5

433ca3c25ff7f5582b10bb89c9f2d239
SHA1

816e579d1ea24b733d22fa1cdd43e3362e5612ef
SHA256

c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8
SHA512

78cfd8955920808dd79f5e1cb38fc72c8d00d11a6515a43e92c1fdb637101a29d3a5d3ccbe06b260ed0d87b07778d51bae3e8cafd1705e4a46ee99962bd1020a
SSDEEP

3072:ZI5/BE9YUdtG716ennADVeMfcRAGKB+uMTEd1CTa:ZiMu1tnADVhERAGKB+uSEdl

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
856	892	WerFault.exe	14

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
892	c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 892 wrote to memory of 856	892	c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe	27
PID 892 wrote to memory of 856	892	c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe	27
PID 892 wrote to memory of 856	892	c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe	27
PID 892 wrote to memory of 856	892	c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe	27

C:\Users\Admin\AppData\Local\Temp\c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe
"C:\Users\Admin\AppData\Local\Temp\c2c5d6dfb8002e6c85c51bc933e47f69a0a015bf859561a2dd705ce32b469fa8.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:892
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 892 -s 188
  2⤵
  - Program crash
  PID:856