f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f

Analysis

max time kernel
148s
max time network
154s
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, 00:32

Target

f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe
Size

1.3MB
MD5

88a2a8cd32d31fa8e3f6b270dc8fc22f
SHA1

aeea756132d5200289e7e1e0c50447b4ff357da8
SHA256

f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f
SHA512

3feb30e1d4898ec6803003f02d6cfb5042a6919c334c01588d30556e839333044d8243d6fcbef57a2deeea0f073c39ce56b718f74b8fe36fff37d682f913c527
SSDEEP

24576:kpyhP5RFFrSEyFPu8JR9ksaQFCLwbLflBPx:ryFPu8D9k5QELuL5

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 2268 set thread context of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80

Suspicious use of SetWindowsHookEx 5 IoCs

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80
PID 2268 wrote to memory of 3348	2268	f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe	80

C:\Users\Admin\AppData\Local\Temp\f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe
"C:\Users\Admin\AppData\Local\Temp\f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2268
- C:\Users\Admin\AppData\Local\Temp\f5f803f70752bf7cc2417c3827a5d30354e4e8d44e944f1aee6d9705d753031f.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:3348

memory/3348-133-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/3348-134-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/3348-135-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/3348-136-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/3348-137-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download