d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389

Analysis

max time kernel
91s
max time network
160s
platform
windows10-2004_x64
resource
win10v2004-20220901-en
resource tags

arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system
submitted
27/11/2022, 20:46

Target

d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
Size

1.3MB
MD5

ec4c5cf8979807c94103a5f920833cd8
SHA1

a784cbaeed0b8e12951dc18019e804b4ff156bac
SHA256

d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389
SHA512

ad7d68c7ab75fbe24c0336f3803cf59f6431a01e7f87b8a476471904604ecbed855d7cd661be27a23346846e7b65b21aaa28e8c77c601625f86f6f8b5eddd65c
SSDEEP

24576:4OiZzDXGLFP53UG7bL1HohIE6BvRx0GOb/4+a0q3bhAqtxe9:Ri1DWLFP53UGe76x0ZUphdt

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4832 set thread context of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
4060	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
4060	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
4060	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
4060	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
4060	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82
PID 4832 wrote to memory of 4060	4832	d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe	82

C:\Users\Admin\AppData\Local\Temp\d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
"C:\Users\Admin\AppData\Local\Temp\d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4832
- C:\Users\Admin\AppData\Local\Temp\d2a69a768b9fd83f6d919927def5becfe0e520c7862c169d3a819328e0cda389.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:4060

memory/4060-136-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

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

Filesize
864KB

Download
memory/4060-138-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/4060-139-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download
memory/4060-140-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

Download