Analysis
-
max time kernel
92s -
max time network
115s -
platform
windows10-2004_x64 -
resource
win10v2004-20240221-en -
resource tags
-
submitted
24/02/2024, 11:43
General
-
Target
2024-02-24_625800d92cca1bb60035f90e97f8a1bf_icedid.exe
-
Size
2.4MB
-
MD5
625800d92cca1bb60035f90e97f8a1bf
-
SHA1
66517fc3e08ddfb0ed1db986756fccaa959bbf16
-
SHA256
ac6134814abf7f4b0e46eafea3889675373dcec3d41583877ed1fcc095011176
-
SHA512
859f9a25fd8b9825e4e304e0c23a113b932847dd1d3d61e9f958deeb6908deec31c9a1ad4cb98b13959aa8bf711a5d8d21245cd3d509504549c95dbd7161d196
-
SSDEEP
49152:PH2BHlLfYcpvmE0SukeNfiAD03yy/cP7BjwV/YnDnHW/I8E6vp1aLmGCaw:PAFLYcv0vfD03yy/cPlFnHW/I8EKaLm
Score
1/10
Malware Config
Signatures
-
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
-
Suspicious use of SetWindowsHookEx 1 IoCs
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-02-24_625800d92cca1bb60035f90e97f8a1bf_icedid.exe"C:\Users\Admin\AppData\Local\Temp\2024-02-24_625800d92cca1bb60035f90e97f8a1bf_icedid.exe"1⤵
- Checks processor information in registry
- Suspicious use of SetWindowsHookEx