8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46

Analysis

max time kernel
140s
max time network
123s
platform
windows7_x64
resource
win7-20240221-en
resource tags

arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system
submitted
01/06/2024, 01:48 UTC

Target

8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe
Size

3.0MB
MD5

c2bc17c0260398f432f0ed8cc21833f3
SHA1

b01884bee34c524787221e1ccd9d33999969e5fb
SHA256

8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46
SHA512

b1a90cb3cb83a04f25db23fac79f9b973aa51ebb6530a32931d33887b53992a70a0591728f14b242a34fe0ab094ddb8843771383c41babdc1d17707b5fd9f1dc
SSDEEP

49152:rFULyI0ftt50XcDxak5Pv8c4Y+OBS283w3aqX01JiXBsyzbVQuokC18ZJTutCVLB:FI0ftD0sgk5PpaObqw3am0b8XzZej8ZV

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2164	2168	WerFault.exe	27

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 2168 wrote to memory of 2164	2168	8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe	28
PID 2168 wrote to memory of 2164	2168	8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe	28
PID 2168 wrote to memory of 2164	2168	8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe	28
PID 2168 wrote to memory of 2164	2168	8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe	28

C:\Users\Admin\AppData\Local\Temp\8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe
"C:\Users\Admin\AppData\Local\Temp\8e235afde8eed6fb7ce6b290388885f2bcf60366035fee375dd89c6201dc2c46.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2168
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 128
  2⤵
  - Program crash
  PID:2164

memory/2168-0-0x0000000001240000-0x0000000001A7E000-memory.dmp

Filesize
8.2MB

Download
memory/2168-3-0x0000000001240000-0x0000000001A7E000-memory.dmp

Filesize
8.2MB

Download