99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3

Analysis

max time kernel
122s
max time network
127s
platform
windows7_x64
resource
win7-20230712-en
resource tags

arch:x64arch:x86image:win7-20230712-enlocale:en-usos:windows7-x64system
submitted
28-08-2023 11:29

Target

99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe
Size

1.8MB
MD5

c0aa528f699bb393ba64827a7dbefcf6
SHA1

80df77438d3cb0b802359a6f0e8ce6af05c53430
SHA256

99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3
SHA512

b06854f4a2268fcf94d30925bf8fc3611953ce92062b345daa3754dc79598a2391c594ee9efdd1580cdd2360efb7117708042076560cdec7fcc8e43bfb8346a6
SSDEEP

24576:Lj6UYzuXxsPx9WEtOolO4VnDIXvTpgO73ATP6cSPuM0SooLcnHdUXzYAz+D4Tlj8:LqzuXU9WQM4VDaX7QCuM7cHdUXziDp

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2012	2080	WerFault.exe	27

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe
2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 2080 wrote to memory of 2012	2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe	28
PID 2080 wrote to memory of 2012	2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe	28
PID 2080 wrote to memory of 2012	2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe	28
PID 2080 wrote to memory of 2012	2080	99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe	28

C:\Users\Admin\AppData\Local\Temp\99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe
"C:\Users\Admin\AppData\Local\Temp\99bc0d09c1442243733d0b5afad161468c3a4f9a5520e1d93dbefb81ff684fd3.exe"
1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2080
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2080 -s 344
  2⤵
  - Program crash
  PID:2012