febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1

Analysis

max time kernel
40s
max time network
46s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
29/10/2022, 18:09

Target

febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe
Size

68KB
MD5

838c3c6071617c2181c473e18c6d749a
SHA1

440aebc2a6253d54c077be8269e68b1b755d4427
SHA256

febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1
SHA512

4be33ef760a538c5872ad227f8866e31828158d91bb42cb4842e4b49c0721a8b2017cbb7d601de1b5022e766ddb7a3a08f6d07824f3f35c41106c5007eac7475
SSDEEP

1536:rcSlkXlCqz1asD4ir1p12Lf+PxyE/aoxEAwitd6JMcHP0rtSC6WLrbIvmaeSvUYY:rDlkIqz1asD4ir1r2LkME/aoxEAwitdZ

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
892	1724	WerFault.exe	17

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
1724	febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 1724 wrote to memory of 892	1724	febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe	28
PID 1724 wrote to memory of 892	1724	febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe	28
PID 1724 wrote to memory of 892	1724	febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe	28
PID 1724 wrote to memory of 892	1724	febb4b82bc7688b674e3720b271e0f4955e0c6cc57c3740f852cbbbb697f17e1.exe	28

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