4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225

Analysis

max time kernel
42s
max time network
46s
platform
windows7_x64
resource
win7-20220901-en
resource tags

arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system
submitted
11-10-2022 01:49

Target

4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe
Size

140KB
MD5

6398299d554485f5378fb04ce410250e
SHA1

02029432612722d981f9bb47c78236d9af0b6387
SHA256

4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225
SHA512

19a91dd5112061de06f3b702663ebc58de6433f89624a0d5dcf701a8145525957df1a34b7e4607bbc01ce9c7941170e1667fd011972352d2813a90d4211d03b8
SSDEEP

3072:vlfzfGL02W2N0fAU9x5Ea3hGCE5j4oQt:FTGL012efAU9x5BxCdU

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1124	832	WerFault.exe	27

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
832	4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 832 wrote to memory of 1124	832	4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe	28
PID 832 wrote to memory of 1124	832	4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe	28
PID 832 wrote to memory of 1124	832	4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe	28
PID 832 wrote to memory of 1124	832	4ab3a00d1b14dd6dd0b98b01c2a5cff2550dc65b8a10892ed4991c316c10f225.exe	28

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