c8fd8860e9a05cc61684ca7a4fea22eda721e701ee717dc039f52312d8d21be6

Analysis

max time kernel
116s
max time network
132s
platform
windows10-2004_x64
resource
win10v2004-20230220-en
resource tags

arch:x64arch:x86image:win10v2004-20230220-enlocale:en-usos:windows10-2004-x64system
submitted
05-05-2023 09:25

Target

IEMonitor.exe
Size

375KB
MD5

7631c33878c331d7396679b0c391fca8
SHA1

77ac7d3e4d50a67751b7577b4e284aaa7245733d
SHA256

c8fd8860e9a05cc61684ca7a4fea22eda721e701ee717dc039f52312d8d21be6
SHA512

4f7ca574794fcd5eddb1bb94919e63fb9ddf35dbd451b25ed30db0ba1b3ab3c373fd7f7d99794456c1ca0532a3b494c5ff85c1906936b504c787172326860892
SSDEEP

6144:1jBIBdVp4/GMlkkcTWponHXVRO2vaMByhCjFp5aapeVbDWTdhqMQaPRGugx:1SFMlkXTWpvmaMByhopIaCbiTdbGF

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
4752	IEMonitor.exe
4752	IEMonitor.exe

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