Analysis
-
max time kernel
148s -
max time network
150s -
platform
windows10-2004_x64 -
resource
win10v2004-20231215-en -
resource tags
-
submitted
30/12/2023, 23:46
General
-
Target
20862f00206aa4168de555a1806a77bd.exe
-
Size
344KB
-
MD5
20862f00206aa4168de555a1806a77bd
-
SHA1
1e6c3d83a3ceb00ea6527dda17eefbf587e09350
-
SHA256
7ec7fa6390a34fadae2313d37bdaf5d10a3dd87391c57e92835c7fafe89fd0e3
-
SHA512
8f732d99b306895472354e40277f8b3aceb4971665495abc72bdc3e8b9f8a16c61aeeff61961d4f00a1c9ea151944f79989b354055d8440e1a131af47564c6f7
-
SSDEEP
6144:UyuQUf1MgsLQcDtVnobOJwth9Pkyu+ZCF5/2JdhryOWpkYQRYUFEg9TBJu4yx:/xQQUbd9PkyzCF5OfkfkDEg9Tru3
Score
7/10
Malware Config
Signatures
-
Checks BIOS information in registry 2 TTPs 1 IoCs
BIOS information is often read in order to detect sandboxing environments.
-
Writes to the Master Boot Record (MBR) 1 TTPs 1 IoCs
Bootkits write to the MBR to gain persistence at a level below the operating system.
-
Checks processor information in registry 2 TTPs 2 IoCs
Processor information is often read in order to detect sandboxing environments.
-
Suspicious use of SetWindowsHookEx 4 IoCs
Processes
-
C:\Users\Admin\AppData\Local\Temp\20862f00206aa4168de555a1806a77bd.exe"C:\Users\Admin\AppData\Local\Temp\20862f00206aa4168de555a1806a77bd.exe"1⤵
- Checks BIOS information in registry
- Writes to the Master Boot Record (MBR)
- Checks processor information in registry
- Suspicious use of SetWindowsHookEx