Skip to main content
Mallory
Malware3 associated CVEs

HybridPetya

Tracked since Nov 25, 2025 · Updated 3 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns3Associated
Actors0Associated
ATT&CK12Techniques
IOCs0Tracked
Type
Ransomware
Capabilities
ExfiltrationPersistenceDefense evasion
Platforms
Windows

HybridPetya is a ransomware strain that combines Petya/NotPetya-style bootlocker behavior with UEFI-focused persistence and Secure Boot bypass techniques. It was reported in 2025 and is characterized by pre-OS execution, destructive disk tampering, and modification of EFI boot components to maintain control of the system before the operating system loads.

On Windows systems, HybridPetya has been described as using an installer that decrypts an embedded DLL and executes it reflectively in memory, reducing reliance on conventional on-disk payload staging. Its payload enumerates local and remote drives, drops ransom notes across user-accessible locations, checks for administrative privileges, accesses the physical disk directly, and performs raw writes to the master boot record and other critical disk regions. It can force a crash and reboot, after which it presents a fake disk-check screen while encryption proceeds and ultimately locks the victim out at boot level with a ransom demand.

A distinguishing feature of HybridPetya is its targeting of the EFI System Partition and boot chain. It has been reported to install a malicious EFI application, replace or modify legitimate boot manager components, and thereby persist beyond normal operating system recovery workflows, including potential survival of OS reinstallation if the boot environment remains compromised. Public reporting has linked the malware to exploitation of Secure Boot bypass conditions involving vulnerable signed boot components, including CVE-2024-7344, enabling execution of untrusted code during boot on affected UEFI-based systems.

HybridPetya is primarily associated with Windows endpoints using UEFI firmware, but its abuse of EFI boot components places it in the broader category of firmware and boot-process threats. No high-confidence attribution to a specific threat actor is established in the available information. It is notable as an example of ransomware adopting bootkit-like tradecraft traditionally associated with stealthier persistence-focused malware.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Associated CVEs

Associated vulnerabilities

3 CVEs Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.

CVE-2026-8863via infosecurity magazine newsUEFI Secure Boot Bypass in Microsoft-Signed Legacy Shim BootloadersTwo CVE IDs, CVE-2026-8863 and CVE-2026-10797, cover the reported shims, and Microsoft revoked the vulnerable binaries in the dbx update shipped with its June 9 Patch Tuesday.View vulnerability →Source ↗
CVE-2026-10797via infosecurity magazine newsUEFI Secure Boot revocation bypass in legacy shimTwo CVE IDs, CVE-2026-8863 and CVE-2026-10797, cover the reported shims, and Microsoft revoked the vulnerable binaries in the dbx update shipped with its June 9 Patch Tuesday.View vulnerability →Source ↗
CVE-2024-7344via medium mk7912Exploited in the wildUEFI Secure Boot bypass in Howyar ReloaderExploited vulnerability: Uses CVE-2024–7344 to bypass Secure Boot and other security protections. | HybridPetya is a new ransomware variant combining traits of Petya and NotPetya with modern firmware-targeting techniques. Discovered: Early 2025, when ESET researchers found samples on VirusTotal.View vulnerability →Source ↗
MITRE ATT&CK

Techniques & procedures

12 distinct techniques documented for this family, organized by ATT&CK tactic.

Persistence

3 techniques
T1542Pre-OS BootEvidence1

11 old, Microsoft-signed, Unified Extensible Firmware Interface (UEFI) applications could be abused to bypass Secure Boot on most systems using the modern firmware standard.

T1542.001System FirmwareEvidence4

Attackers could bypass UEFI Secure Boot on a wide range of systems thanks to 11 Microsoft-signed UEFI shim bootloaders carrying vulnerabilities that have remained buried for more than a decade... Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits ... even with Secure Boot switched on.

T1542.003BootkitEvidence3

Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits such as Bootkitty, HybridPetya and BlackLotus, even with Secure Boot switched on.

Stealth

8 techniques
T1036MasqueradingEvidence1

Once the system reboots after the destructive payload has executed, the malware continues its deception by showing a fake CHKDSK screen.

T1070Indicator RemovalEvidence1

In some execution paths, the routine also targets the EFI system partition, renaming legitimate boot manager files (bootmgfw.efi) and replacing them with its own malicious payloads.

T1211Exploitation for StealthEvidence1

Exploited vulnerability: Uses CVE-2024–7344 to bypass Secure Boot and other security protections.

T1497.001System ChecksEvidence1

These checks prevent wasted effort on unsuitable targets, such as small virtual drives havin disk size less than 40 mb as shown in Figure 7.

T1542Pre-OS BootEvidence1

11 old, Microsoft-signed, Unified Extensible Firmware Interface (UEFI) applications could be abused to bypass Secure Boot on most systems using the modern firmware standard.

T1542.001System FirmwareEvidence4

Attackers could bypass UEFI Secure Boot on a wide range of systems thanks to 11 Microsoft-signed UEFI shim bootloaders carrying vulnerabilities that have remained buried for more than a decade... Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits ... even with Secure Boot switched on.

T1542.003BootkitEvidence3

Exploitation allows untrusted code to run during boot, opening the door to UEFI bootkits such as Bootkitty, HybridPetya and BlackLotus, even with Secure Boot switched on.

T1620Reflective Code LoadingEvidence1

When executed, the installer decrypts this DLL into memory and uses reflective loading technique to initialize and run it without ever writing the DLL to disk.

Discovery

3 techniques
T1083File and Directory DiscoveryEvidence1

For each valid drive, the code constructs full paths to standard directories (Desktop, Downloads, Documents, Public) and appends the fixed filename “YOUR_FILES_ARE_ENCRYPTED.TXT”.

T1120Peripheral Device DiscoveryEvidence1

It then enumerates all logical drives using GetLogicalDriveStringsA and filters them by type (DRIVE_REMOVABLE, DRIVE_FIXED, DRIVE_REMOTE) to identify candidate locations for ransom note placement.

T1497.001System ChecksEvidence1

These checks prevent wasted effort on unsuitable targets, such as small virtual drives havin disk size less than 40 mb as shown in Figure 7.

Impact

2 techniques
T1486Data Encrypted for ImpactEvidence1

Impact: Begins encrypting files before the operating system loads, making recovery extremely difficult.

T1561.001Disk Content WipeEvidence1

The malware performs raw writes to multiple fixed offsets on the disk. These include sector 0 (the MBR itself) and additional offsets like 0x200, 0x2400, 0x4000, 0x4200, and 0x4400.

Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matchingMatch every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities3CVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping12Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.