41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59

Analysis

max time kernel
119s
max time network
135s
platform
windows10-1703_x64
resource
win10-20230915-en
resource tags

arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system
submitted
15-10-2023 15:40

Target

41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe
Size

295KB
MD5

4c989fb8f6a193a9f942d8ad3634a6d8
SHA1

18491f3d1cddea26a869c38d1b35013aaac7c892
SHA256

41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59
SHA512

5d3a528a4f2c889ba40ac90d83acc4663604ed89166f14e2bbe564dcba85c4c943bacdd70717c79ea6b2c21e85da14e7e23b3a4880d101cb385e11057b289194
SSDEEP

6144:aZEe3bpi5aaYcTdGUdCGIl8DOb9YlemBz8HNI8TJn:aZEe32dG6ClgOhYlemJ8tI8TJn

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4464 set thread context of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72

Program crash 1 IoCs

pid	pid_target	Process	procid_target
1708	4464	WerFault.exe	69

Suspicious use of WriteProcessMemory 13 IoCs

description	pid	Process	procid_target
PID 4464 wrote to memory of 3776	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	71
PID 4464 wrote to memory of 3776	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	71
PID 4464 wrote to memory of 3776	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	71
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72
PID 4464 wrote to memory of 4848	4464	41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe	72

C:\Users\Admin\AppData\Local\Temp\41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe
"C:\Users\Admin\AppData\Local\Temp\41fc562abffcd7b720c528f07a0bb738144fbb85274bb9a5cb0de007cc711c59.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4464
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:3776
- C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:4848
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 4464 -s 144
  2⤵
  - Program crash
  PID:1708

memory/4848-4-0x0000000000400000-0x0000000000432000-memory.dmp

Filesize
200KB

Download
memory/4848-3-0x0000000000400000-0x0000000000432000-memory.dmp

Filesize
200KB

Download
memory/4848-5-0x0000000000400000-0x0000000000432000-memory.dmp

Filesize
200KB

Download
memory/4848-0-0x0000000000400000-0x0000000000432000-memory.dmp

Filesize
200KB

Download
memory/4848-6-0x0000000000400000-0x0000000000432000-memory.dmp

Filesize
200KB

Download