2a4fe31fc68d8bb5968a361288835e29ef79342088b6fd958361855f5fc4c264

Analysis

max time kernel
173s
max time network
191s
platform
windows10-2004_x64
resource
win10v2004-20221111-en
resource tags

arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system
submitted
01-12-2022 13:40

Target

2a4fe31fc68d8bb5968a361288835e29ef79342088b6fd958361855f5fc4c264.chm
Size

64KB
MD5

7b43a9345ffe9460454cee2d17d11be7
SHA1

1b03f692104bd8c8d7ab29136c13691580868d0a
SHA256

2a4fe31fc68d8bb5968a361288835e29ef79342088b6fd958361855f5fc4c264
SHA512

43fba0a45aed7fcc08d4ef6618c6234e39724fa4f3f873858aaa080e182d0029593e8612dc00d2f904acf1d52f5cf14caf918b71589a26db07e832878b83f99d
SSDEEP

1536:pSaoW4+lpWNPqmLzAKCt/PDTR+pDnWM66P0:b4+lYNPBzHWZ3Mt8

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
4856	hh.exe
4856	hh.exe

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