64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053

Analysis

max time kernel
139s
max time network
151s
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:36

Target

64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
Size

1.2MB
MD5

7eebc082b73ed42145cccee2f4d93327
SHA1

a8d57255742addccdeadffff797bae6b9deedc8c
SHA256

64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053
SHA512

f7f94f5a69cd5e9757c4dd7fb8d48a58836fe81e4e021c7c5bc8dbb170155acc3cedcb07c3fde98258197303a45f157086e1a25ae8a9ae8a340449683097ffbd
SSDEEP

24576:2pEdL1+miBQxprjUQftJLpV1VnaLcpI4Ig+JxM:UEqmvxD3pRaLcZIg+

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 1496 set thread context of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
5072	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
5072	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
5072	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
5072	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
5072	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78
PID 1496 wrote to memory of 5072	1496	64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe	78

C:\Users\Admin\AppData\Local\Temp\64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
"C:\Users\Admin\AppData\Local\Temp\64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1496
- C:\Users\Admin\AppData\Local\Temp\64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe
  "C:\Users\Admin\AppData\Local\Temp\64c2b64a41efb964156972671fbf3b1e2297a13c0f011450d1fff59e2e6eb053.exe"
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:5072

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

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

Filesize
892KB

Download
memory/5072-138-0x0000000000400000-0x00000000004DF000-memory.dmp

Filesize
892KB

Download