9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492

Analysis

max time kernel
40s
max time network
46s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
19-10-2022 14:04

Target

9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe
Size

204KB
MD5

a19c515eba9660a396999167a2321300
SHA1

d33d0b91a4bb9208dd8d0deafc6a32dcf732e571
SHA256

9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492
SHA512

1eaec08e4f530fc3c0f1916cfec95a683c3b4ebbc52a31f80f9b333606649a2b1706347685eade1d5dbb1522c3a916f902ea14b91e81e50bcd3d64bc196ec1e7
SSDEEP

3072:NVeWCzDNpVPU+mzihKh8wpzDqulR3X9sDpLg6ZGKIXeYnVlDY:NVe/5EV82llbs1g6+XbVS

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1928	704	WerFault.exe	23

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
704	9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 704 wrote to memory of 1928	704	9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe	27
PID 704 wrote to memory of 1928	704	9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe	27
PID 704 wrote to memory of 1928	704	9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe	27
PID 704 wrote to memory of 1928	704	9e69bee4efee0f09a20251ff14475e6f71ab8d5a13b6c751a6806ad161539492.exe	27

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