c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c

Analysis

max time kernel
45s
max time network
48s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
29-11-2022 07:05

Target

c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c.exe
Size

677KB
MD5

2976f2b1d793c84ed5599def7c10f480
SHA1

a085d5142384f024748a625395936933ee893b2c
SHA256

c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c
SHA512

2fd38f79c477e56000d8d5660e80f831fbffc4212fff2f443aa571a29a276202a4c4b7332fbe58207bd8ef742a1e4f80f0c9065e4daa75db8d09648ff56edf7f
SSDEEP

6144:WS0cT/lkS1W192aS4JhjOOYdRCwsjJbsfPUZMWAe09qcLtKdpJd3f6Ub+jfSyY/r:B0cBW1EROYvejJgfPkxkwytGpDd4g5

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
748	536	WerFault.exe	27

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 536 wrote to memory of 748	536	c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c.exe	28
PID 536 wrote to memory of 748	536	c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c.exe	28
PID 536 wrote to memory of 748	536	c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c.exe	28
PID 536 wrote to memory of 748	536	c2a0bfe2c697b7c3f727bbcecbaf34de1276f0233f96adc6ed2dc98a1b1d3c5c.exe	28

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

memory/536-54-0x0000000075B11000-0x0000000075B13000-memory.dmp

Filesize
8KB

Download
memory/536-56-0x0000000000400000-0x00000000004AD000-memory.dmp

Filesize
692KB

Download