General
-
Target
HITMAN.3.v3.10-v3.160.Plus.13.Trainer-FLiNG.zip
-
Size
743KB
-
Sample
240702-zen2nsyala
-
MD5
e58656461a495c6d55aff0d14e562827
-
SHA1
bc92b3807d93a1e8f889b8ff5df0e6e946937285
-
SHA256
f3e494d790c5ae93c9a2df78d92c4747e0c63e74ebdcf72a882d5e2d222c9368
-
SHA512
e80f6e7d9853fb0303ef2eb9cade5b462498a503d9f8281b6f9c87b837db887df6fd628c31882d9b1cc7556c8ad08589ee3a4303643130cdf6efb9583e58fe5a
-
SSDEEP
12288:nKdZTDpluPBrdtVhWxwdA0oibc/nmlWvbc0qqAH6o7s6bHBnDAMExwdP4oUqw:yZOrTVoxsxo4c+WDc0q3aKbHlDAE4om
Behavioral task
behavioral1
Sample
HITMAN 3 v3.10-v3.160 Plus 13 Trainer.exe
Resource
win10v2004-20240611-en
Malware Config
Targets
-
-
Target
HITMAN 3 v3.10-v3.160 Plus 13 Trainer.exe
-
Size
1.2MB
-
MD5
3a6da0bdd054d3f1bb0f4667c00dbf77
-
SHA1
888a1e905691c8b2b3b4daf556469be493fb10fb
-
SHA256
446e83f044b6319c85d16ace8fc63537a0d8b541658a90dae375756495535003
-
SHA512
1a384a49b4b5a81f8cf559bb476c57a3f7b73250eb86c625bffaa32a0cd679480076c9aaa49209fa73c79db1bf199724078763c1ecb05e7045911453c57f070a
-
SSDEEP
24576:HqgTM8/TP5XsxDzwHhCeiqKl6lKiWj3MryahDSVXT5X:HjTT/TP5cxDze2qKjE1GXT5X
-
Suspicious use of NtCreateProcessExOtherParentProcess
-
XMRig Miner payload
-
Boot or Logon Autostart Execution: Active Setup
Adversaries may achieve persistence by adding a Registry key to the Active Setup of the local machine.
-
Command and Scripting Interpreter: PowerShell
Run Powershell to modify Windows Defender settings to add exclusions for file extensions, paths, and processes.
-
Downloads MZ/PE file
-
Drops file in Drivers directory
-
Event Triggered Execution: Image File Execution Options Injection
-
Modifies RDP port number used by Windows
-
Sets service image path in registry
-
Uses Session Manager for persistence
Creates Session Manager registry key to run executable early in system boot.
-
Checks BIOS information in registry
BIOS information is often read in order to detect sandboxing environments.
-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
Drops startup file
-
Event Triggered Execution: Component Object Model Hijacking
Adversaries may establish persistence by executing malicious content triggered by hijacked references to Component Object Model (COM) objects.
-
Executes dropped EXE
-
Impair Defenses: Safe Mode Boot
-
Loads dropped DLL
-
Modifies file permissions
-
Adds Run key to start application
-
Checks for any installed AV software in registry
-
Checks installed software on the system
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
Drops desktop.ini file(s)
-
Enumerates connected drives
Attempts to read the root path of hard drives other than the default C: drive.
-
Maps connected drives based on registry
Disk information is often read in order to detect sandboxing environments.
-
Writes to the Master Boot Record (MBR)
Bootkits write to the MBR to gain persistence at a level below the operating system.
-
Checks system information in the registry
System information is often read in order to detect sandboxing environments.
-
Drops file in System32 directory
-
MITRE ATT&CK Enterprise v15
Execution
Command and Scripting Interpreter
1PowerShell
1System Services
1Service Execution
1Persistence
Boot or Logon Autostart Execution
4Active Setup
1Registry Run Keys / Startup Folder
3Create or Modify System Process
1Windows Service
1Event Triggered Execution
3Component Object Model Hijacking
1Image File Execution Options Injection
1Netsh Helper DLL
1Pre-OS Boot
1Bootkit
1Privilege Escalation
Boot or Logon Autostart Execution
4Active Setup
1Registry Run Keys / Startup Folder
3Create or Modify System Process
1Windows Service
1Event Triggered Execution
3Component Object Model Hijacking
1Image File Execution Options Injection
1Netsh Helper DLL
1Defense Evasion
File and Directory Permissions Modification
1Impair Defenses
2Safe Mode Boot
1Modify Registry
5Pre-OS Boot
1Bootkit
1