2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595

Analysis

max time kernel
174s
max time network
214s
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, 10:54

Target

2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe
Size

1.1MB
MD5

dc625ff2f82537f2c7720db3ad81a4f9
SHA1

88b77259724592d74d6ede5f5f51de09ff53f031
SHA256

2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595
SHA512

dbe00a14048f87098f8cb9f5ba9cc4cbbe85763d69292814aaaaa91de6a42ff62ec25970b3bd444593c1b78c9b6b2e660ef534a542139aaa7a8548123ae72cfd
SSDEEP

12288:1Bbm4/qx4e1wW/OJ7XG0KcJjIi5i52gmdS/uHoGD5isJ3ZCHNKm0:1w4/qx4e1wW/kVbL5i5Oss8A

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 3136 set thread context of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2164	3136	WerFault.exe	14

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 3136 wrote to memory of 3000	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	89
PID 3136 wrote to memory of 3000	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	89
PID 3136 wrote to memory of 3000	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	89
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90
PID 3136 wrote to memory of 1776	3136	2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe	90

C:\Users\Admin\AppData\Local\Temp\2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe
"C:\Users\Admin\AppData\Local\Temp\2b00bcf2125a8dfce6278a6d9faa00fedb1c1ea0b8e9fb266ccd181c60260595.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3136
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3000
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:1776
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 3136 -s 144
  2⤵
  - Program crash
  PID:2164

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

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

Filesize
204KB

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

Filesize
204KB

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

Filesize
204KB

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

Filesize
204KB

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

Filesize
204KB

Download
memory/1776-5-0x0000000000400000-0x0000000000433000-memory.dmp

Filesize
204KB

Download