52ab779b01f38da1abebb9b03eee90dfc8170f69711d87b0c13b2f3496762ffe

Analysis

max time kernel
132s
max time network
149s
platform
windows10-2004_x64
resource
win10v2004-20231222-en
resource tags

arch:x64arch:x86image:win10v2004-20231222-enlocale:en-usos:windows10-2004-x64system
submitted
19/01/2024, 20:05

Target

68850482ec037fc451e25b64d45e824d.exe
Size

24KB
MD5

68850482ec037fc451e25b64d45e824d
SHA1

4d3b340a5e418feb803218d497ad16aba934bf3b
SHA256

52ab779b01f38da1abebb9b03eee90dfc8170f69711d87b0c13b2f3496762ffe
SHA512

e39823ae4071cdb9400e77b219305d69b448a8fa3a936495e697c73860c2adec794958fc44b2ff3a65f6c78d2f3025ca8f82767ca3a8250ae951a8e0c0b079f2
SSDEEP

192:Ubtt+ELGsDi8DHbpI3RZLt9FgEmaNjZoW3DwraB/9K:UbttDD74mVaNj2W3Dwre/9K

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
4436	68850482ec037fc451e25b64d45e824d.exe
4436	68850482ec037fc451e25b64d45e824d.exe

C:\Users\Admin\AppData\Local\Temp\68850482ec037fc451e25b64d45e824d.exe
"C:\Users\Admin\AppData\Local\Temp\68850482ec037fc451e25b64d45e824d.exe"
1⤵
- Suspicious use of SetWindowsHookEx
PID:4436