25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e

Analysis

max time kernel
363s
max time network
386s
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, 05:32

Target

25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe
Size

46KB
MD5

b0dec1051e62547de051e3b3e9b76651
SHA1

d8ed668ed9b8c9b1bf8d994f4e81b4dc04bc83aa
SHA256

25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e
SHA512

6dcac231dee03fe6db32aa15c9afd1d65ab7be088b2e282872a8c85228312fdff5d261498f9b737ac727bd0c4a702251e7ff46597822f3532f578c3aaf822029
SSDEEP

768:3oeAD4vAxr0A9aMiGcpq/6i3D1GozIn/1s0S8JsaLmvYbOWFbGDYbL3:3oeADPo0JiGT/v3DQoS9pS8aaLmvKTmc

Score

3^/10

Program crash 2 IoCs

pid	pid_target	Process	procid_target
1928	2032	WerFault.exe	81
4500	2032	WerFault.exe	81

Suspicious use of WriteProcessMemory 3 IoCs

description	pid	Process	procid_target
PID 2032 wrote to memory of 1928	2032	25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe	87
PID 2032 wrote to memory of 1928	2032	25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe	87
PID 2032 wrote to memory of 1928	2032	25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe	87

C:\Users\Admin\AppData\Local\Temp\25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe
"C:\Users\Admin\AppData\Local\Temp\25afbe4ac9eab7cd1a413be635afc1dadfaee523406f892d2ebbab1fb2b8225e.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2032
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2032 -s 336
  2⤵
  - Program crash
  PID:1928
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2032 -s 336
  2⤵
  - Program crash
  PID:4500

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 432 -p 2032 -ip 2032
1⤵
PID:1668