0d51569cedd582fb9b85b7cb5356dac5a2f9eb097e55d7fe95b3786b14dcf785

Analysis

max time kernel
148s
max time network
153s
platform
windows10-2004_x64
resource
win10v2004-20220812-en
resource tags

arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
submitted
29/08/2022, 20:05

Target
xnQs4m1UEV5X.exe
Size 469KB
Sample220829-yttp2aecfm
SHA256 0d51569cedd582fb9b85b7cb5356dac5a2f9eb097e55d7fe95b3786b14dcf785
MD5 c8e36332de649225373464600d00fe11
SHA1 ccf18db59b45573c1649ad12c43b04839d5afd03
SHA512 09636c29c511b32593f036afb67a5db42e784f48b2cb07ee64da5ca40d0b2e7109a74fd1baf6aed53703f463b6ccb5214dd7b093a779f5ee5dd7a9e2f9462505
SSDEEP 12288:umnk7iLJbpIpiRL6I2WhSKQ9ZsfZQSZn9:WiLJbpI7I2WhQqZ7Z9
MD5 SHA1 SHA512 SSDEEP

Score

1^/10

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
1928	xnQs4m1UEV5X.exe

C:\Users\Admin\AppData\Local\Temp\xnQs4m1UEV5X.exe
"C:\Users\Admin\AppData\Local\Temp\xnQs4m1UEV5X.exe"
1⤵
- Suspicious use of SetWindowsHookEx
PID:1928