a6013b13d91f8232bd5ad03b1a8af4365a1eac6d05604346d6a152e26ec0134d

Analysis

max time kernel
120s
max time network
128s
platform
windows7_x64
resource
win7-20240221-en
resource tags

arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system
submitted
29-05-2024 01:46

Target

315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe
Size

305.3MB
MD5

ade0c5f3a9d3459a4d32060667b0f006
SHA1

0efa4ab38ccbb8dd208120eddb6fbe297d7ed685
SHA256

315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe
SHA512

6a3ccfc0631e1eb4df936e114bf35dc91dccc058dae2134c7836794643c2c71e8ff81c922bd374a31ae2171f01bf60f1ee05590568b97380c0341d12fea9efdc
SSDEEP

24576:coSJMFMFTWSgXQWooooooooooooooooooooooooooooooooooooooooooooooooS:+JMFk7

Score

1^/10

Suspicious use of WriteProcessMemory 3 IoCs

Processes:

315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe

description	pid	Process	procid_target
PID 2076 wrote to memory of 2300	2076	315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe	28
PID 2076 wrote to memory of 2300	2076	315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe	28
PID 2076 wrote to memory of 2300	2076	315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe	28

C:\Users\Admin\AppData\Local\Temp\315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe
"C:\Users\Admin\AppData\Local\Temp\315d36da6305f267f36216733590babcbcb405c4fc88935d2f3a7bf610cf98fe.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:2076
- C:\Windows\system32\WerFault.exe
  C:\Windows\system32\WerFault.exe -u -p 2076 -s 532
  2⤵
  PID:2300

memory/2076-0-0x000007FEF51A3000-0x000007FEF51A4000-memory.dmp

Filesize
4KB

Download
memory/2076-1-0x000000013F500000-0x0000000140500000-memory.dmp

Filesize
16.0MB

Download
memory/2076-2-0x000007FEF51A3000-0x000007FEF51A4000-memory.dmp

Filesize
4KB

Download