a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475

Analysis

max time kernel
166s
max time network
218s
platform
windows10-2004_x64
resource
win10v2004-20221111-en
resource tags

arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system
submitted
01-12-2022 19:53

Target

a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe
Size

710KB
MD5

528429c7e572abd5fe01739d07366f5e
SHA1

3e489bef4560afdc25eb0457ca43f24a2906fc63
SHA256

a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475
SHA512

530a6b0fddf5add8b02f11f7b56a2d25c29de9bef0b9533364cdd6a0c1a49781714505a501ee37ecd17f005444fad3549d786055b1fc8132b9a21733b96b5fd1
SSDEEP

12288:dphsZo6I0Q8zXO7mPsNjAY1/setghtXpNSrws99A4FCG:dpCZTVFzXSmPiJRZtw5NLs99A8d

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2060	452	WerFault.exe	81

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 452 wrote to memory of 176	452	a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe	82
PID 452 wrote to memory of 176	452	a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe	82
PID 452 wrote to memory of 176	452	a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe	82

C:\Users\Admin\AppData\Local\Temp\a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe
"C:\Users\Admin\AppData\Local\Temp\a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:452
- C:\Users\Admin\AppData\Local\Temp\a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe
  C:\Users\Admin\AppData\Local\Temp\a8e3b0c7341fae83e3a6d556e3ced6383278fe08ccf50811520941b6aa858475.exe
  2⤵
  PID:176
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 452 -s 488
  2⤵
  - Program crash
  PID:2060

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 424 -p 452 -ip 452
1⤵
PID:3736