2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e

Analysis

max time kernel
185s
max time network
194s
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:51

Target

2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe
Size

1.2MB
MD5

4691c456dc9b88346ba7eaef78874c2e
SHA1

0b576b4dfb4a63fb331a6504c8e4abbb1985ff7a
SHA256

2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e
SHA512

ac2ffa56e69f32b7e5a926fecdb61cef39ed3e95307b84da70378d341d3139822916f11a6bc75ea71155db48d62d75c4462bcc3d96159444238024c1a2ec0564
SSDEEP

24576:GpEdL1+miBQxprjUQftJLpV1VnaLcpI4Ig+JxMt:kEqmvxD3pRaLcZIg+i

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 5060 set thread context of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
5076	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe
5076	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe
5076	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe
5076	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe
5076	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81
PID 5060 wrote to memory of 5076	5060	2afb709b850ae37bb097933796a4f362cd30e63a22ebf160ec3e3b64e59db48e.exe	81

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

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

Download