General
- Target boykisser.exe
- Size 3.0MB
- Sample260701-e2mf5sgs7x
- SHA256 b4f66394b20e42b4dcf255aa8c820a9aa0b932cb923caf9346b971f340f9df63
- MD5 019bebc6d9f6c9a9e2346a41682a83e7
- SHA1 4e166d6ebdabdb652d17d96d9f8e123d21c52f41
- SHA512 b9ba26dc182a6100af0ae065f5b7f491beec6be000c65f35b87a05cbe6203c01f3a40a4553e236344bcd23d3d04c3e1fa60e4bc38bb306f4c08977ef891f17ec
- SSDEEP 49152:CiwPH4viAsUCY6BbvMAZGAWCqaf0YF6BoR924SkZaDXN5+NMfTnf8nJloHB8NC:SQvqjMWqTaPJ2TW+Zf8n39
- TLSH T1B2E533317C7837BFC35B11F3530ED2261A4FA5325338A60F225C9EE997A16B5D82426E
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
boykisser.exe
Resource
win10v2004-20260513-en
Behavioral task
behavioral2
Sample
boykisser.exe
Resource
win11ltsc2024-20260629-en
Malware Config
Targets
-
- Target boykisser.exe
- Size 3.0MB
- SHA256 b4f66394b20e42b4dcf255aa8c820a9aa0b932cb923caf9346b971f340f9df63
- MD5 019bebc6d9f6c9a9e2346a41682a83e7
- SHA1 4e166d6ebdabdb652d17d96d9f8e123d21c52f41
- SHA512 b9ba26dc182a6100af0ae065f5b7f491beec6be000c65f35b87a05cbe6203c01f3a40a4553e236344bcd23d3d04c3e1fa60e4bc38bb306f4c08977ef891f17ec
- SSDEEP 49152:CiwPH4viAsUCY6BbvMAZGAWCqaf0YF6BoR924SkZaDXN5+NMfTnf8nJloHB8NC:SQvqjMWqTaPJ2TW+Zf8n39
- TLSH T1B2E533317C7837BFC35B11F3530ED2261A4FA5325338A60F225C9EE997A16B5D82426E
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Disables Task Manager via registry modification
-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
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
-
Loads dropped DLL
-
Modifies system executable filetype association
-
Adds Run key to start application
-
Checks installed software on the system
Looks up Uninstall key entries in the registry to enumerate software on the system.
-
Obfuscated Files or Information: Command Obfuscation
Adversaries may obfuscate content during command execution to impede detection.
-
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.
MITRE ATT&CK Enterprise v16
Persistence
Boot or Logon Autostart Execution
1Registry Run Keys / Startup Folder
1Event Triggered Execution
3Change Default File Association
1Component Object Model Hijacking
1Netsh Helper DLL
1Pre-OS Boot
1Bootkit
1Privilege Escalation
Boot or Logon Autostart Execution
1Registry Run Keys / Startup Folder
1Event Triggered Execution
3Change Default File Association
1Component Object Model Hijacking
1Netsh Helper DLL
1Defense Evasion
Modify Registry
4Obfuscated Files or Information
1Command Obfuscation
1Pre-OS Boot
1Bootkit
1Credential Access
Credentials from Password Stores
1Credentials from Web Browsers
1Unsecured Credentials
1Credentials In Files
1