ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc

Analysis

max time kernel
90s
max time network
138s
platform
windows10-2004_x64
resource
win10v2004-20220901-en
resource tags

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

Target

ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
Size

1.3MB
MD5

54a5c787495af5791290aad5d9654032
SHA1

d01c1b49592734560a4e72ff2cec39b45746fa1d
SHA256

ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc
SHA512

309b8fd7183486f094b823dba6e60a7043d8eab24fd5c90047b958fc70173bd2322224db3ffafff38935f1bd873437a2d121efdc795f44fdaa761722ca6c863f
SSDEEP

24576:7rKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPaku:7rKo4ZwCOnYjVmJPaN

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 3548 set thread context of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
4172	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
4172	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
4172	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
4172	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
4172	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80
PID 3548 wrote to memory of 4172	3548	ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe	80

C:\Users\Admin\AppData\Local\Temp\ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
"C:\Users\Admin\AppData\Local\Temp\ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3548
- C:\Users\Admin\AppData\Local\Temp\ca2a7ff1e24a3f66a714e21ed05d88f46afa1a85989e1c32acac6a73832080cc.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:4172

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

Filesize
868KB

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

Filesize
868KB

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

Filesize
868KB

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

Filesize
868KB

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

Filesize
868KB

Download