cad2b6b2e9fbc51734757d518386ce7940fb6d0bfa887268d313faa7e19d4ec7

Analysis

max time kernel
138s
max time network
124s
platform
windows10-2004_x64
resource
win10v2004-20240802-en
resource tags

arch:x64arch:x86image:win10v2004-20240802-enlocale:en-usos:windows10-2004-x64system
submitted
10-08-2024 00:49

Target

both executors.sfx.exe
Size

20.3MB
MD5

031e8de494548e53e70a0fb6b663eda4
SHA1

0d5c7733fefbaec2fcb7b65f827ac555aadcaebf
SHA256

cad2b6b2e9fbc51734757d518386ce7940fb6d0bfa887268d313faa7e19d4ec7
SHA512

8915d0cae49f55166546496940721293a5bbcf14bfd337022458d944d410b42b1ae4768d062c8f2eafec4380e346f59bfe8a676ab2cafcd84956e53eb2a4d064
SSDEEP

393216:9OrF7Xbsfeg2E3Zr62Q07vnUPHzWjtb2c75AOxeOlNUnBS8T/RnB:9ORI328Zr6JtTWjtb2c75AOI7n0+/RnB

Score

1^/10

Suspicious use of SetWindowsHookEx 2 IoCs

pid	Process
764	both executors.sfx.exe
764	both executors.sfx.exe

C:\Users\Admin\AppData\Local\Temp\both executors.sfx.exe
"C:\Users\Admin\AppData\Local\Temp\both executors.sfx.exe"
1⤵
- Suspicious use of SetWindowsHookEx
PID:764