a79f8ceef906992dd4a3609d4eafa51ef39d09a0e616dbc9a832f6c717b65308

Analysis

max time kernel
147s
max time network
154s
platform
windows10-2004_x64
resource
win10v2004-20240611-en
resource tags

arch:x64arch:x86image:win10v2004-20240611-enlocale:en-usos:windows10-2004-x64system
submitted
13/06/2024, 23:24

Target
dbf2imc.exe
Size 344KB
Sample240613-3dzzbsyerr
SHA256 69e3f3215500c23a987658176cdd70759865f116b6c9a30fc5290ab24fcd1c57
MD5 dfcf39471d0c9c7c35b4b3071cf227a9
SHA1 769de05e0abadfa81056f8e7c618410e07c1edfc
SHA512 6470373bb227b279afa5f3022d2501f38dee91dba766f7d0fa1fdf2cc9034888b9a277d1b8b45eacb214c213f0fb7ce205bcc6e432f403aa22546df2bd53d0d1
SSDEEP 6144:C1bN9b/zmhAabe6R0zt/6itpR7zhp7MYXszg6H:I3/zmq8e63itjkg6
MD5 SHA1 SHA512 SSDEEP

Score

1^/10

Suspicious use of SetWindowsHookEx 1 IoCs

pid	Process
1916	dbf2imc.exe

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