Skip to main content
Mallory
Malware1 associated actor

Rovnix

Tracked since Nov 25, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns0Associated
Actors1Associated
ATT&CK33Techniques
IOCs14Tracked
Type
Bootkit
Capabilities
PersistenceDefense evasionProcess injectionPrivilege escalationDLL sideloadingExfiltration
Delivery
MalspamLure
Platforms
Windows

Rovnix is a Windows bootkit framework best known for its use as the bootkit component of Carberp. It infects the NTFS Volume Boot Record and subverts the boot sequence to load unsigned kernel-mode drivers, including on 64-bit Windows systems with driver-signing enforcement. Its boot-time execution provides persistent, privileged access and conceals subsequently deployed malware.

Rovnix uses bootloader manipulation, interrupt hooks, and hardware breakpoints to bypass code-integrity checks. Its kernel-mode components support payload injection into user-mode processes and concealed storage for malicious components. Depending on the variant, storage resides outside the normal filesystem or in an encrypted filesystem container protected by kernel hooks. These hooks can hide files and registry objects and prevent unauthorized access, deletion, or modification. Polymorphic bootstrap code and encrypted components further hinder detection. Some versions support downloading and executing multiple additional payloads.

Rovnix has been distributed through malicious email attachments and downloader infections, including campaigns using Andromeda. Documented activity includes financial-data theft targeting Windows users in the United Kingdom and other countries. Some later data-stealing variants omitted the original bootkit component. A 2020 campaign used Russian-language coronavirus and World Bank-themed lures to distribute Rovnix-derived malware, adding a UAC bypass through a mock trusted directory and DLL side-loading before installing the bootkit and injecting a loader.

Rovnix source code became publicly available and has been reused in other malware. Its use therefore spans multiple operators and modified implementations rather than identifying a single threat actor.

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
Threat actors

Associated threat actors

1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
Carberp

Rovnix was the first bootkit family to use VBR (Volume Boot Record) infection (NTFS bootstrap code) for loading unsigned kernel-mode drivers on x64 (64 bit) platforms.

via eset welivesecurity blogwelivesecurity.com
MITRE ATT&CK

Techniques & procedures

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

Resource Development

1 technique
T1587.001MalwareEvidence1

Sitnikov was allegedly charged for posting the source code of the Anubis banking trojan on Freedom F0x, a Telegram channel where Sitnikov often posted data leaks and malware source code

Initial Access

1 technique
T1566PhishingEvidence2

In mid-April, our threat monitoring systems detected malicious files being distributed under the name “on the new initiative of the World Bank in connection with the coronavirus pandemic”

Execution

6 techniques
T1059.003Windows Command ShellEvidence1

the malware creates and runs a series of BAT files that start wusa.exe from the fake directory and then clean up the traces

T1059.005Visual BasicEvidence1

Detect suspicious VBA keywords often used by malware ... detect_suspicious checks if VBA macro code contains specific keywords often used by malware to act on the system | olevba is a script to parse OLE and OpenXML files such as MS Office documents (e.g. Word, Excel), to detect VBA Macros, extract their source code in clear text...

T1106Native APIEvidence2

With the aid of the Windows API, the malware creates the directory C:\Windows \System32

T1204.002Malicious FileEvidence2

AutoOpen | Runs when the Word document is opened ... Auto_Open | Runs when the Excel Workbook is opened ... Workbook_Open | Runs when the Excel Workbook is opened

T1574Hijack Execution FlowEvidence1

The IPL code is loaded and executed by the VBR: thus, by modifying value of the ‘Hidden Sectors’ field, the malware is able to intercept execution flow at boot time.

T1574.001DLLEvidence1

DLL hijacking is additionally used: a malicious library is placed in the fake directory under the name of one of the libraries imported by the legitimate file

Persistence

5 techniques
T1542Pre-OS BootEvidence2

Bootkits are a type of malware that infects the boot process of a computer, allowing attackers to gain persistent access and control over the system.

T1542.003BootkitEvidence3

All bootkits aim to modify and subvert operating system components before the OS can be loaded. The most interesting target components are as follows: BIOS/UEFI, MBR (Master Boot Record) and the operating system boot loader.

T1542.004ROMMONkitEvidence1

Win32/Rovnix is the first known bootkit to target the VBR.

T1543Create or Modify System ProcessEvidence1

Most bootkit infections have used MBR-modification... The Rovnix family used other ways to infect with modification of the VBR

T1547.001Registry Run Keys / Startup FolderEvidence1

Malicious components are initialized at boot time in order to load the malicious kernel-mode driver from the hidden storage area, and thus bypass the Microsoft kernel-mode code signing policy enforced on x64 platforms.

Privilege Escalation

5 techniques
T1055Process InjectionEvidence2

KLoader is written to the disk; its purpose is to inject the payload into running processes.

T1068Exploitation for Privilege EscalationEvidence1

This price is only for the bootkit package and excludes the cost of exploits for escalating privilege in order to get access allowing modifications deep into the system.

T1543Create or Modify System ProcessEvidence1

Most bootkit infections have used MBR-modification... The Rovnix family used other ways to infect with modification of the VBR

T1547.001Registry Run Keys / Startup FolderEvidence1

Malicious components are initialized at boot time in order to load the malicious kernel-mode driver from the hidden storage area, and thus bypass the Microsoft kernel-mode code signing policy enforced on x64 platforms.

T1548.002Bypass User Account ControlEvidence1

One of them is a UAC bypass mechanism that uses the “mocking trusted directory” technique.

Stealth

15 techniques
T1014RootkitEvidence2

The first bootkits started to emerge on the malware scene as cybercriminals realized that bootkit development was a way in which they could increase the profitability of a kernel-mode rootkit by widening the range of its targets to include users of 64-bit machines.

T1027Obfuscated Files or InformationEvidence2

This packet is XOR-encrypted with the single-byte key 0xF7

T1036MasqueradingEvidence1

The file “on the new initiative of the World Bank in connection with the coronavirus pandemic.exe” is a self-extracting archive

T1055Process InjectionEvidence2

KLoader is written to the disk; its purpose is to inject the payload into running processes.

T1070.004File DeletionEvidence1

clean up the traces by deleting the created directory and the easymule.exe dropper itself.

T1218System Binary Proxy ExecutionEvidence1

the malware ... copies there a legitimate signed executable file from C:\Windows\System32 ... (in this case, wusa.exe)

T1480.002Mutual ExclusionEvidence2

For synchronization reasons the payload generates the mutex: Global<Generated_string>.

T1542Pre-OS BootEvidence2

Bootkits are a type of malware that infects the boot process of a computer, allowing attackers to gain persistent access and control over the system.

T1542.003BootkitEvidence3

All bootkits aim to modify and subvert operating system components before the OS can be loaded. The most interesting target components are as follows: BIOS/UEFI, MBR (Master Boot Record) and the operating system boot loader.

T1542.004ROMMONkitEvidence1

Win32/Rovnix is the first known bootkit to target the VBR.

T1564Hide ArtifactsEvidence1

So as to store payload and configuration information secretly Win32/Gapz implements hidden storage.

T1564.001Hidden Files and DirectoriesEvidence1

The base functionality of BkSetup.dll is centred on the process of infection and setting up the hidden storage partition.

T1574Hijack Execution FlowEvidence1

The IPL code is loaded and executed by the VBR: thus, by modifying value of the ‘Hidden Sectors’ field, the malware is able to intercept execution flow at boot time.

T1574.001DLLEvidence1

DLL hijacking is additionally used: a malicious library is placed in the fake directory under the name of one of the libraries imported by the legitimate file

T1620Reflective Code LoadingEvidence1

its resources contain a bitmap image that is actually an executable file, which it unpacks and loads into memory.

Credential Access

1 technique
T1056Input CaptureEvidence1

The whole attack is designed to steal financial information, mainly credit card numbers.

Collection

2 techniques
T1056Input CaptureEvidence1

The whole attack is designed to steal financial information, mainly credit card numbers.

T1560Archive Collected DataEvidence1

The file ... is a self-extracting archive that dishes up easymule.exe and 1211.doc.

Command and Control

6 techniques
T1071Application Layer ProtocolEvidence4

The payload module includes functionality for downloading and executing additional modules from the C&C server... The C&C domain is rtttt-windows.com

T1071.001Web ProtocolsEvidence1

it then starts a C&C communication cycle, within which a data packet about the infected device is generated... and sent to C&C.

T1090.003Multi-hop ProxyEvidence1

Avalanche used fast-flux DNS, a technique to hide the criminal servers, behind a constantly changing network of compromised systems acting as proxies.

T1105Ingress Tool TransferEvidence4

It can steal user information and download a variety of other malicious software such as Zeus, Rovnix, Dyzap or Cutwail.

T1568.001Fast Flux DNSEvidence4

Avalanche used fast-flux DNS, a technique to hide the criminal servers, behind a constantly changing network of compromised systems acting as proxies.

T1568.002Domain Generation AlgorithmsEvidence1

The latest campaign targeting the UK uses the US Declaration of Independence as a reference when generating botnet Command & Control (C&C) domain names.

Indicators of compromise

Observables

14 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
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 matching14Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors1Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs 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 mapping33Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.