e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1

Analysis

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

arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system
submitted
11/06/2024, 04:29

Target

e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe
Size

184KB
MD5

714ae8c49c071a80fd2a9a523b747cb3
SHA1

ffa63795b4fb8f5b465ddba8d229a83559076011
SHA256

e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1
SHA512

d64b8ef17271a8dbf855223e4a38aaf13f4b926d4479ded1277cc4a15bd1559c216369de6be7825182d026499351ceac71d21f963f90454b53f18a43d266f30b
SSDEEP

3072:5IOV5kojo+dUE7T1W7n8M3t+kvNqnbiu:5I1ovB7TU8at+klqnbiu

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
3040	2020	WerFault.exe	27

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
2020	e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 2020 wrote to memory of 3040	2020	e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe	28
PID 2020 wrote to memory of 3040	2020	e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe	28
PID 2020 wrote to memory of 3040	2020	e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe	28
PID 2020 wrote to memory of 3040	2020	e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe	28

C:\Users\Admin\AppData\Local\Temp\e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe
"C:\Users\Admin\AppData\Local\Temp\e69cbe40ca02ae5db721866cbd3756010ba8f7358882c62f86b3b73ce5ff92b1.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2020
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2020 -s 240
  2⤵
  - Program crash
  PID:3040