7bcb16d0c7d421091b04fcd6f9405cc2440eafe0b3cdf9c48f026eec8802a31d

Analysis

max time kernel
149s
max time network
153s
platform
windows10-2004_x64
resource
win10v2004-20240412-en
resource tags

arch:x64arch:x86image:win10v2004-20240412-enlocale:en-usos:windows10-2004-x64system
submitted
21/04/2024, 17:30

Target

TimerResolution.exe
Size

32KB
MD5

2c9017dbc6c38d2567d550177d64a81d
SHA1

f77de1de8e39c17c299c25696cc7965bfe07028f
SHA256

8a0c6871ec6e09e4193f537884111006a947d7b3e9260110907777d0c4dd68d3
SHA512

244430ea44c510b61351941cd459278e2cd7bf88750643c49b2d710139b3c71b4a35e8379d2dccbce23a15105e1b6ad6c9444875dabaefeb311a45a9a0fc580a
SSDEEP

192:h0ZL+FnJA4o2TCFFlsDof85qan7hsDofi1oynazAetV0qMI18rii13:h0enJA4/2fkJn618zAo0qM68rv13

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
2972	TimerResolution.exe
2972	TimerResolution.exe

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