478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e

Analysis

max time kernel
118s
max time network
119s
platform
windows7_x64
resource
win7-20240220-en
resource tags

arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system
submitted
06/07/2024, 21:19

Target

478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe
Size

184KB
MD5

d3d41ca259c5916bf69171beb4eb7ff4
SHA1

c1d5b971e9cfacb90e6aa579d8f54fa406857520
SHA256

478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e
SHA512

01f0417dd632fc0850c7a54c26a0c54b652cc572c877fc35485a64afa9b5eb7f416cd636c241617f26cfb908513267237b0f62a58bdbf8e29ad2b82bcb780b55
SSDEEP

3072:L8+l21VoxNLDeN4vkCV8Eq6x7vbqnvivSn/:L8+0onq4vN8P6x7TqnvivS

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1656	3068	WerFault.exe	27

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
3068	478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 3068 wrote to memory of 1656	3068	478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe	28
PID 3068 wrote to memory of 1656	3068	478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe	28
PID 3068 wrote to memory of 1656	3068	478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe	28
PID 3068 wrote to memory of 1656	3068	478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe	28

C:\Users\Admin\AppData\Local\Temp\478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe
"C:\Users\Admin\AppData\Local\Temp\478fb964e0696e9bc2da50af9c81568030d9f791149c03443b386824d894b30e.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3068
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 3068 -s 200
  2⤵
  - Program crash
  PID:1656