Analysis
-
max time kernel
67s -
max time network
50s -
platform
windows10-2004_x64 -
resource
win10v2004-20240419-en -
resource tags
-
submitted
26-04-2024 22:47
General
-
Target
2024-04-26_a51acbfe17c514419a83392629536aa2_icedid.exe
-
Size
2.3MB
-
MD5
a51acbfe17c514419a83392629536aa2
-
SHA1
e673d43537a4f791f86aafc2c9cfd34f814b5baf
-
SHA256
12d86f7760bdbaf2ccc26ab67568a611d89f1dc600f7b0dde56cd1046655244f
-
SHA512
a1bdea7ebe16a003b9a14b6c34892eb1b62d3d8ae8635660f1e5060d0d42dd16fba5595c59d531f074724ae0ae059a3344cb6669e4d4815007bfe2cca3c120fa
-
SSDEEP
49152:sH2BHlLfYcpvmE0SukeNfiAD03yy/cP7jjwV/YnDnHW/I8E6/p1aLcD3:sAFLYcv0vfD03yy/cP/FnHW/I8EqaLu3
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-04-26_a51acbfe17c514419a83392629536aa2_icedid.exe"C:\Users\Admin\AppData\Local\Temp\2024-04-26_a51acbfe17c514419a83392629536aa2_icedid.exe"1⤵
- Checks processor information in registry
- Suspicious use of SetWindowsHookEx