e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7

Analysis

max time kernel
217s
max time network
230s
platform
windows10-2004_x64
resource
win10v2004-20230915-en
resource tags

arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
submitted
12/10/2023, 07:45

Target

e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe
Size

1.0MB
MD5

9d0a9e513bd76d243c2e78341358f7cc
SHA1

2f5c7872844cc9acee3d951040703a59875684ed
SHA256

e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7
SHA512

c92c58ae7f45e38f0931a26cd3fa017e3d59508b4563a212e306ded32adf6dbc6b32fff45e6de6d0dcbbaa1bee5ea102c50cd35c041ff077fe344afe9d47f239
SSDEEP

12288:toendPenEp953bXeu5W2fo8oBNFJQxBTTASKuLpv+WE2yMGbg1qbw55:RdPenEp953bpfo8Un+TMSj+bT2

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 5040 set thread context of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89

Program crash 1 IoCs

pid	pid_target	Process	procid_target
756	5040	WerFault.exe	15

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 5040 wrote to memory of 2320	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	88
PID 5040 wrote to memory of 2320	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	88
PID 5040 wrote to memory of 2320	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	88
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89
PID 5040 wrote to memory of 3672	5040	e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe	89

C:\Users\Admin\AppData\Local\Temp\e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe
"C:\Users\Admin\AppData\Local\Temp\e4d2e96be91dd0945bbd52f51e5ae0b85ca3df6f83a8c3161fac01a79dfedad7.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5040
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:2320
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3672
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 5040 -s 268
  2⤵
  - Program crash
  PID:756

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 468 -p 5040 -ip 5040
1⤵
PID:1836

memory/3672-0-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/3672-1-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/3672-2-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/3672-3-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download
memory/3672-4-0x0000000000400000-0x000000000042F000-memory.dmp

Filesize
188KB

Download