e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb

Analysis

max time kernel
28s
max time network
30s
platform
windows7_x64
resource
win7-20221111-en
resource tags

arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system
submitted
22-12-2022 15:15

Target

e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe
Size

456KB
MD5

04405255a0de3d1500f3aebed009126d
SHA1

fdf616ae9d695bdcded718907a21a79f35716cde
SHA256

e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb
SHA512

184ffcfed0881fc667bea2c44f1f0638bcb92e2bd4e41d53c2404469d333cd456c7a5638d0dab4574357eb1606d42ab646c53f061755298352cb91897a94ef3c
SSDEEP

12288:EWnxfgsRL4u/1AlLK6FRY2n8OPKxGvYmB0:fxgsRftD0C2nKG

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1516	616	WerFault.exe	27

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
616	e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 616 wrote to memory of 1516	616	e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe	28
PID 616 wrote to memory of 1516	616	e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe	28
PID 616 wrote to memory of 1516	616	e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe	28
PID 616 wrote to memory of 1516	616	e747a81b7c17e51e712d531639c3d2ac87c0ad6d3a9abd310a601450fb99d0bb.exe	28

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