0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51

Analysis

max time kernel
187s
max time network
189s
platform
windows10-2004_x64
resource
win10v2004-20220812-en
resource tags

arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
submitted
26/11/2022, 01:59

Target

0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
Size

1.2MB
MD5

2ee1c0176d1082b27f546836062917bd
SHA1

23ed006e613cbe166d17b2d8ccb789eb9c177a1c
SHA256

0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51
SHA512

0672ac7c1212ab3d13b2c52b687a2ed5384b4e4f57cb49c8d78e988e4821350a4a06f6e373202d9698f9946546dda9de519809c185287e2283b8feedbb1b8c2d
SSDEEP

24576:2pEdL1+miBQxprjUQftJLpV1VnaLcpI4Ig+JxM:UEqmvxD3pRaLcZIg+

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4644 set thread context of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
5076	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
5076	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
5076	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
5076	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
5076	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79
PID 4644 wrote to memory of 5076	4644	0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe	79

C:\Users\Admin\AppData\Local\Temp\0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
"C:\Users\Admin\AppData\Local\Temp\0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4644
- C:\Users\Admin\AppData\Local\Temp\0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe
  "C:\Users\Admin\AppData\Local\Temp\0fbc341def8cab3f8250ff022ac5fe7a58bdefa55f13e6c69cbdc489ff856b51.exe"
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:5076

memory/5076-136-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download
memory/5076-137-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download
memory/5076-138-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download
memory/5076-139-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download
memory/5076-140-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download
memory/5076-141-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download