0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c

Analysis

max time kernel
143s
max time network
148s
platform
windows10-2004_x64
resource
win10v2004-20230915-en
resource tags

arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
submitted
08-10-2023 17:24

Target

0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe
Size

423KB
MD5

9e9bb522cd58b74106ad8d87386d20e5
SHA1

2245412836d19bf23a6a41da65d1adc7c93bc2c6
SHA256

0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c
SHA512

18c8129a0217801dfade4c4edfdee638fdb6ab2cca00a323749fcc943c7ea1934e22bdd0badf20d51c43829546a96aebe40dfd85de77654eee7cbfb0bef0f565
SSDEEP

6144:5D3fpu01XFBvaKAwQtdsJlfpoCJAO78Ykw/S3R3wBHBxfukBEJuHcGW+d2Cs4AQM:5D3xf1XFBC2JQCJOfw/ZBHbYJO2HIrlS

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 2100 set thread context of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87

Program crash 1 IoCs

pid	pid_target	Process	procid_target
4752	2100	WerFault.exe	84

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 2100 wrote to memory of 4652	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	86
PID 2100 wrote to memory of 4652	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	86
PID 2100 wrote to memory of 4652	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	86
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87
PID 2100 wrote to memory of 636	2100	0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe	87

C:\Users\Admin\AppData\Local\Temp\0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe
"C:\Users\Admin\AppData\Local\Temp\0eafcd86b0e0f0205c2a8914d2ea4ae0270b14890da1c467d379e4c11d4c857c.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2100
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:4652
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:636
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2100 -s 420
  2⤵
  - Program crash
  PID:4752

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 444 -p 2100 -ip 2100
1⤵
PID:4704

memory/636-0-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download
memory/636-1-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download
memory/636-2-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download
memory/636-3-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download
memory/636-4-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download