ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1

Analysis

max time kernel
37s
max time network
47s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
01/12/2022, 22:55

Target

ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe
Size

272KB
MD5

c662dd0597ddc4d8c389aa6c5f66f95c
SHA1

1e07b2d508ed898083f3a7276a83eb758bd747a8
SHA256

ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1
SHA512

bdd675bd7c45b1d4970add452f7ef93d5c4d255ec75e18c182dface6ac56c404e4d6f6ed3e5f82742c30dd0274c033a2fd93759a1e0c65cf0198a26823831a7c
SSDEEP

6144:RLamlQxchRdjLmtrBuMrdekUH63u+X5sc57s:gTxGLTuPL5w

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1504	384	WerFault.exe	15

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
384	ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 384 wrote to memory of 1504	384	ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe	27
PID 384 wrote to memory of 1504	384	ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe	27
PID 384 wrote to memory of 1504	384	ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe	27
PID 384 wrote to memory of 1504	384	ad2ae18040fa9ec40dcc4e647d4bbacb600dc5a0069e3c938e9be26ed57983a1.exe	27

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