2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c

Analysis

max time kernel
119s
max time network
120s
platform
windows7_x64
resource
win7-20231215-en
resource tags

arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system
submitted
18/02/2024, 05:36

Target

2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe
Size

5KB
MD5

49e939a437244a49cb4e1c86258ea0d8
SHA1

78153a75a6775e0767caf8faba7547a9c3b8bb96
SHA256

2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c
SHA512

cc854f038bf1c383498a0a753ba08e40ee4237c06a7995c81e58a022e8a335994b82075252606fd3c1e374a469f557f9789eee69e46183b4285dd7c065f93083
SSDEEP

48:SLlXWFPpT+dXVfzZh4yMGcKzMEkTaak4PAZivO2pB42pBdvMZL2R7twRuqSxp:UWLkFfNnOKYloIQ2pm2pbYScxE

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
312	2468	WerFault.exe	19

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 2468 wrote to memory of 312	2468	2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe	28
PID 2468 wrote to memory of 312	2468	2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe	28
PID 2468 wrote to memory of 312	2468	2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe	28
PID 2468 wrote to memory of 312	2468	2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe	28

C:\Users\Admin\AppData\Local\Temp\2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe
"C:\Users\Admin\AppData\Local\Temp\2f1d48046a5f07c9b23a4e7055dc72e3b69423de1c4b48f20cf1154808e5b07c.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2468
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2468 -s 48
  2⤵
  - Program crash
  PID:312