56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6

Analysis

max time kernel
132s
max time network
166s
platform
windows10-2004_x64
resource
win10v2004-20231023-en
resource tags

arch:x64arch:x86image:win10v2004-20231023-enlocale:en-usos:windows10-2004-x64system
submitted
28/10/2023, 21:26

Target

56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe
Size

5KB
MD5

910403a3ba422453e05a041eb1150a9d
SHA1

0efe24191ddb4a9da8d3d503efce8751e6bc5fc0
SHA256

56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6
SHA512

b69286c5416ccc2ddd7964811580c37605058ec4c7c3a843673c3ff18b1f98a8a033283ab9892d6e001767bba0b56041784ee9e0c725d0d10ab77b9d1cd918a5
SSDEEP

48:SZlXWFPpT+dXVfzZh4yMGcKzMEkTaak4PAZivO2pB42pBdvMZL2R7tqBRuqSxp:aWLkFfNnOKYloIQ2pm2pbYSmbxE

Score

3^/10

Program crash 2 IoCs

pid	pid_target	Process	procid_target
640	392	WerFault.exe	85
4044	392	WerFault.exe	85

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 392 wrote to memory of 640	392	56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe	91
PID 392 wrote to memory of 640	392	56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe	91
PID 392 wrote to memory of 640	392	56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe	91

C:\Users\Admin\AppData\Local\Temp\56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe
"C:\Users\Admin\AppData\Local\Temp\56180d8a0cf10c07ff86cbb80217bbbaa37317a8e968f9a877d88638bf3514c6.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:392
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 392 -s 224
  2⤵
  - Program crash
  PID:640
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 392 -s 224
  2⤵
  - Program crash
  PID:4044

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 392 -ip 392
1⤵
PID:4200