Analysis
-
max time kernel
200s -
max time network
216s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
-
submitted
04-12-2022 12:31
General
-
Target
a1ce6f9787ff0690971dc19702b5d3613fde68998dfaf4cae1502769f15beef2.exe
-
Size
222KB
-
MD5
96c342a561beec43d9bdcf1749d3a825
-
SHA1
a13d8f16c7a84998f0bca6368eed8641a513facc
-
SHA256
a1ce6f9787ff0690971dc19702b5d3613fde68998dfaf4cae1502769f15beef2
-
SHA512
09b7332ff9ee89f74cb165d1a8fe196dc4554e10373181ec7c68116eb7adc700ba981cff4e956dc86811d6ff7fda6b3fc5bbf05ba9f06ffe3a2a7dfd1a73b8b7
-
SSDEEP
6144:alMaxD94Q9+sBQrmBKGxlShqWU+AAG2Z+aO8UUjsvQI:+MaxDqQxXKGiQ3AG8Uz
Malware Config
Signatures
-
UPX packed file 2 IoCs
Detects executables packed with UPX/modified UPX open source packer.
-
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\a1ce6f9787ff0690971dc19702b5d3613fde68998dfaf4cae1502769f15beef2.exe"C:\Users\Admin\AppData\Local\Temp\a1ce6f9787ff0690971dc19702b5d3613fde68998dfaf4cae1502769f15beef2.exe"1⤵
- Checks BIOS information in registry
- Writes to the Master Boot Record (MBR)
- Checks processor information in registry
- Suspicious use of SetWindowsHookEx
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
828KB
-
Filesize
828KB