952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0

Analysis

max time kernel
165s
max time network
171s
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 08:54

Target

952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
Size

1.3MB
MD5

8782d686e785888f6db658d5b1348486
SHA1

551f24745edcccfb41a90ee9702d29a0920a4536
SHA256

952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0
SHA512

151febd6b2b4496f8efbdd7104312a84dc899c11be2363b7a82cc56254bccae4ef1b83f9d3d54dc7394620b29a60c92bbb60e8575fae57cd6ad528b2d26381b7
SSDEEP

24576:pDASdSysJOcj0VQpWbl7s2LP0CXuiAayiWASALUgv2j6R6XEVeRs9HgVfgV2:uSQtk2zQytkgis6yxI2

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 2652 set thread context of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
5096	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
5096	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
5096	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
5096	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
5096	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84
PID 2652 wrote to memory of 5096	2652	952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe	84

C:\Users\Admin\AppData\Local\Temp\952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
"C:\Users\Admin\AppData\Local\Temp\952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2652
- C:\Users\Admin\AppData\Local\Temp\952f6c4a897f1ab51a0c54b585f0a26f759b8d6f4c38eb3c9765a5d74abe6eb0.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:5096

memory/5096-132-0x0000000000000000-mapping.dmp

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

Filesize
864KB

Download
memory/5096-133-0x0000000000400000-0x00000000004D8000-memory.dmp

Filesize
864KB

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

Filesize
864KB

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

Filesize
864KB

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

Filesize
864KB

Download