cb82f3f7be0e77affd8576059e5f4e09a0be1ad1da816ce86cde8037674b7fdf

Analysis

max time kernel
136s
max time network
153s
platform
windows10-2004_x64
resource
win10v2004-20231215-en
resource tags

arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system
submitted
31/12/2023, 06:00

Target

2afd47c2e46a0cce8a23670ce6c80118.chm
Size

13KB
MD5

2afd47c2e46a0cce8a23670ce6c80118
SHA1

10bf01a9bf7066bd3832c3197b52fb60d08a739c
SHA256

cb82f3f7be0e77affd8576059e5f4e09a0be1ad1da816ce86cde8037674b7fdf
SHA512

2c4225b06b3f8259afd781ef64df3c97307b84694e88c679b5baec90885a7c0cb401dab069aa7f928f297f8d63e57e08d602f5989ab4a816f332dc3b83e34c0e
SSDEEP

96:V+Q/Yni2yKcxabLxBihItvHpzq5VkqAKzFDSFJ/Vi069ywEyk:VZAni2Mx0xBLHpzq5eqj4WT9Bdk

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
2404	hh.exe
2404	hh.exe

C:\Windows\hh.exe
"C:\Windows\hh.exe" C:\Users\Admin\AppData\Local\Temp\2afd47c2e46a0cce8a23670ce6c80118.chm
1⤵
- Suspicious use of SetWindowsHookEx
PID:2404