bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814

Analysis

max time kernel
44s
max time network
49s
platform
windows7_x64
resource
win7-20220901-en
resource tags

arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system
submitted
05-12-2022 07:19

Target

bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe
Size

13KB
MD5

cc59d846c3cdf6163be0797d60b8c6bb
SHA1

8015ce446ed457587158aafc8926528e4c42d7d1
SHA256

bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814
SHA512

61f9296771cfc274e8bfeeef78937cd2c7b21634ed6159be9b1227e5f1d1b6f8f3c53abb0030b540f01c34786f88274ef86e142d66da21770717694f604d501e
SSDEEP

192:mfkUnf2LoqiNsdJaCr240cR4wn8pAxzh014cRYHyBI5yi7GiVoztySH:g/nf2L66r0q4UFcm8IpCieA

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2036	2012	WerFault.exe	12

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 2012 wrote to memory of 2036	2012	bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe	27
PID 2012 wrote to memory of 2036	2012	bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe	27
PID 2012 wrote to memory of 2036	2012	bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe	27
PID 2012 wrote to memory of 2036	2012	bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe	27

C:\Users\Admin\AppData\Local\Temp\bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe
"C:\Users\Admin\AppData\Local\Temp\bdc6f6da2fa74b57fd6ecf1c422547650d18c9ad5e4fa0ba302e908211a7c814.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2012
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2012 -s 88
  2⤵
  - Program crash
  PID:2036