5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d

Analysis

max time kernel
117s
max time network
150s
platform
windows10-2004_x64
resource
win10v2004-20221111-en
resource tags

arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system
submitted
22/11/2022, 12:56

Target

5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
Size

1.3MB
MD5

876ff124ca219d04c3acefef25b99dc8
SHA1

3d24514038f3ef6a0e431d06d07005cfe940e26f
SHA256

5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d
SHA512

6054e54c6a2e81ff890936b44d9d843b2037716af180e23bf67e5a984e826e51b81267f97b4510a1d352d5526e7cf825b78191a94b2f05bdcc7534a4537f9180
SSDEEP

24576:7rKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPak:7rKo4ZwCOnYjVmJPa

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4368 set thread context of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
2384	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
2384	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
2384	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
2384	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
2384	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82
PID 4368 wrote to memory of 2384	4368	5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe	82

C:\Users\Admin\AppData\Local\Temp\5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
"C:\Users\Admin\AppData\Local\Temp\5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4368
- C:\Users\Admin\AppData\Local\Temp\5045967ea8d4ee4589eacadab504ddd273e5c1ed1ed4b06fe272bb5ce64fc33d.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:2384

memory/2384-133-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/2384-134-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/2384-135-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/2384-136-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/2384-137-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/2384-138-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download