b3ea576403e902647b96d20c3eb10e31ec78165bb61ea77439295d6677db7176

Analysis

max time kernel
141s
max time network
151s
platform
windows10-2004_x64
resource
win10v2004-20231222-en
resource tags

arch:x64arch:x86image:win10v2004-20231222-enlocale:en-usos:windows10-2004-x64system
submitted
06-01-2024 02:29

Target

450afd5fef864833dd677c09d6f53bcd.exe
Size

196KB
MD5

450afd5fef864833dd677c09d6f53bcd
SHA1

abdc5f7c159b71dbe7f609522ac035300516be42
SHA256

b3ea576403e902647b96d20c3eb10e31ec78165bb61ea77439295d6677db7176
SHA512

e635063982c89cccdb54cb3c23942cb5ef4156b060803159c4309a25bbd2751ed7c65564c74247e12dc449f6bf95abf8c357fbb0cbc9915906e8c246cc98a2d3
SSDEEP

1536:aWD3DJpfpOjQIoIYZaU52NNNNN+NNNNNNN2NNNNNNNNN5XKwr/2VAAAAdAH0GlXj:aWjrgWIBUyXKwrpVr9MQXH9

Score

1^/10

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
2100	450afd5fef864833dd677c09d6f53bcd.exe

C:\Users\Admin\AppData\Local\Temp\450afd5fef864833dd677c09d6f53bcd.exe
"C:\Users\Admin\AppData\Local\Temp\450afd5fef864833dd677c09d6f53bcd.exe"
1⤵
- Suspicious use of SetWindowsHookEx
PID:2100