2dc65011521e7ad60108888f5371fb028a91e927b1073cb9289f80fd02ee1763

Analysis

max time kernel
120s
max time network
122s
platform
windows7_x64
resource
win7-20240215-en
resource tags

arch:x64arch:x86image:win7-20240215-enlocale:en-usos:windows7-x64system
submitted
13-05-2024 08:13

Target

af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe
Size

493KB
MD5

751240a12c22d583c8bd9a764351f4d3
SHA1

12634abd225dceda347cb5b16bf036d5a247340b
SHA256

af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30
SHA512

7c3eb6e4c3b4cdd14f30d2bce08852e007443494b9fe1314efba77d0b40b0604f6108ace8483cd14f6125cc5fa32b8e10b331744771bf91ff056286fda20f975
SSDEEP

12288:tvDTGTc8/jVKygRliE66auiqpvZXhu7aVuVmi9l1IPa0Xp:tvDB8/l0a/SZhHVuYO0T

Score

3^/10

Program crash 1 IoCs

Processes:

WerFault.exe

pid	pid_target	Process	procid_target
2244	1268	WerFault.exe	27

Suspicious use of WriteProcessMemory 4 IoCs

Processes:

af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe

description	pid	Process	procid_target
PID 1268 wrote to memory of 2244	1268	af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe	29
PID 1268 wrote to memory of 2244	1268	af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe	29
PID 1268 wrote to memory of 2244	1268	af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe	29
PID 1268 wrote to memory of 2244	1268	af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe	29

C:\Users\Admin\AppData\Local\Temp\af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe
"C:\Users\Admin\AppData\Local\Temp\af9c5ff480fec8f9f7f8c274ed08c18a4e5a894eec2eb3577031e60657b87b30.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:1268
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 1268 -s 52
  2⤵
  - Program crash
  PID:2244

memory/1268-0-0x0000000000030000-0x0000000000031000-memory.dmp

Filesize
4KB

Download
memory/1268-1-0x0000000000030000-0x0000000000031000-memory.dmp

Filesize
4KB

Download