The XMRig wormable campaign (February 2026) delivers a cryptominer through pirated software bundles, uses BYOVD to evade defenses, and employs time-based logic bombs to activate mining stealthily and survive reboots.
Users and organizations that install pirated software; any Windows host that permits vulnerable driver loads.
Cryptojacking steals compute and increases costs while BYOVD and logic-bomb timing keep the malware hidden for long periods.
- Block pirated-software installation and enforce application allow-listing.
- Enable Microsoft's vulnerable-driver blocklist with WDAC/HVCI.
- Alert on sustained high CPU usage and unusual driver loads.
- Audit startup items and scheduled tasks for unauthorized entries.
Key Technical Findings
Cryptojacking (XMRig) campaign using BYOVD and time-based logic bombs.
Windows endpoints installing pirated software with loadable vulnerable drivers.
Pirated software bundles distributed via compromised sites/file-sharing.
Dropper exploits a vulnerable driver to run the mining payload (T1203).
Time-based logic bombs and autostart execution (T1547.001) ensure recurring activation.
Kernel access via vulnerable driver (implied by BYOVD).
BYOVD to bypass security tools; timed activation to avoid detection.
Not specified in the source material.
Wormable spread (per campaign name; specifics not detailed in the source material).
Not specified in the source material.
High – resource hijacking with stealthy, persistent operation.
Technical Background
The campaign baits users with pirated software that drops an XMRig miner. It uses BYOVD to execute via a legitimate-but-vulnerable driver, gaining kernel access and evading endpoint defenses, while time-based logic bombs trigger mining according to usage patterns to avoid notice and persist across reboots (T1547.001).
Defenses combine application allow-listing, the vulnerable-driver blocklist/HVCI, and behavioral detection (sustained high CPU, unusual driver loads, unauthorized autostart entries).
Attack Chain Analysis
-
Initial Access
ActivityDistribute pirated software containing the miner.
EvidenceInstall of cracked/pirated bundles.
TelemetryEDR, software inventory.
Detection opportunityFlag pirated-software installs.
-
Execution
ActivityDropper exploits a vulnerable driver to run the payload (T1203).
EvidenceVulnerable driver load.
TelemetrySysmon EID 6, EDR.
Detection opportunityAudit driver loads against the blocklist.
-
Persistence
ActivityUse logic bombs and autostart (T1547.001).
EvidenceUnauthorized startup/scheduled entries.
TelemetryRun keys, Security 4698.
Detection opportunityReview startup items for unauthorized entries.
-
Defense Evasion
ActivityBYOVD to bypass security tools; timed activation.
EvidenceMining only during certain windows.
TelemetryEDR, performance metrics.
Detection opportunityCorrelate periodic CPU spikes with driver abuse.
-
Impact
ActivityMine cryptocurrency, hijacking resources.
EvidenceSustained high CPU/GPU usage.
TelemetryPerformance counters, EDR.
Detection opportunityAlert on abnormal sustained CPU.
Deep Technical Behavior Analysis
The defining behaviors are BYOVD-based kernel evasion and time-gated activation that hides mining behind normal usage. Detection benefits from driver-load telemetry plus performance analytics that catch periodic CPU spikes correlated with suspicious driver activity.
Worm-propagation specifics, driver hashes, and miner indicators are Potential – requires validation and not fully specified in the source material.
Indicators of Compromise
Indicators of Behavior
Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).
| Behavioral Indicator | Description | Data Source | Confidence |
|---|---|---|---|
| Anomalous PowerShell execution | Encoded/obfuscated commands, download cradles, or unusual parent-child process lineage. | Sysmon EID 1, PowerShell 4104 | Potential |
| Suspicious child process lineage | Office or web/service processes spawning script hosts or shells. | Sysmon EID 1, EDR | Potential |
| Security log clearing | Event log cleared or audit policy changed to hinder visibility. | Windows Security 1102, 4719 | Potential |
| New service / scheduled task creation | Unexpected persistence via services or tasks. | Security 7045, 4698; Sysmon | Potential |
| Beaconing to rare destinations | Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. | Proxy, firewall, DNS logs | Potential |
| Unusual DNS queries | High-entropy or rare domains; possible tunneling. | DNS resolver logs | Potential |
Detection Engineering Guidance
Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.
Recommended Log Sources
| Platform | Log Source | What to Look For | Priority |
|---|---|---|---|
| Windows | Security Event Log | Logon (4624/4625), service (7045), task (4698), log clear (1102) | High |
| Windows | Sysmon | Process creation (1), network (3), image load (7), LSASS access (10) | High |
| Windows | PowerShell Operational | Script block logging (4104), module logging | High |
| Endpoint | EDR / Defender telemetry | Process tree, persistence, tamper attempts | High |
| Network | DNS resolver logs | Rare/high-entropy domains, tunneling | Medium |
| Network | Proxy / firewall logs | Beaconing, direct-IP C2, exfil volume | High |
MITRE ATT&CK Mapping
| Tactic | Technique ID | Technique Name | Relevance | Detection Opportunity | Confidence |
|---|---|---|---|---|---|
| Execution | T1203 | Exploitation for Client Execution | Exploitation of vulnerabilities in software to execute malicious code. | Monitoring application logs for unusual access patterns or errors. | Reported |
| Persistence | T1547.001 | Boot or Logon Autostart Execution | Utilization of time-based logic to ensure malware execution on startup. | Reviewing startup items and scheduled tasks for unauthorized entries. | Reported |
Incident Response Guidance
- Validate exposure and confirm whether the issue applies to your environment.
- Preserve evidence (memory, disk, relevant logs) before remediation.
- Isolate affected hosts/accounts if compromise is suspected.
- Collect volatile data and review the log sources listed above.
- Hunt for the indicators of behavior and any related atomic indicators.
- Rotate potentially exposed credentials, keys, and session tokens.
- Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
- Patch affected systems; reimage where integrity cannot be assured.
- Run post-remediation validation and a BAS/security-validation retest.
Remediation and Hardening
- Patch affected systems and reduce internet-exposed services.
- Enforce MFA and least-privilege for privileged and remote access.
- Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
- Restrict script execution and constrain LOLBins where feasible.
- Monitor persistence locations and disable unnecessary services.
- Segment critical assets and review privileged accounts.
- Rotate secrets and remove credentials from configuration files.
- Tune SIEM/EDR detections, then validate controls after changes.
Business Risk
- Service disruption: degraded or unavailable systems during compromise or recovery.
- Data exposure: risk to sensitive, regulated, or customer data depending on scope.
- Regulatory exposure: potential breach-notification and compliance obligations.
- Financial impact: incident response, downtime, and potential extortion costs.
- Brand and trust impact: reputational damage with customers and partners.
Executive Takeaway
What leadership needs to know: Cryptojacking steals compute and increases costs while BYOVD and logic-bomb timing keep the malware hidden for long periods. Current assessed risk: High.
Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.
Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.
Validating Your Defenses with Valitrix
The Valitrix Breach and Attack Simulation (BAS) platform provides organizations with a robust method for validating their security controls against real-world threats, such as those posed by the XMRig wormable campaign. By emulating specific MITRE ATT&CK techniques, including BYOVD exploits and time-based logic bombs, Valitrix allows security teams to test their detection and response capabilities in a controlled environment.
This proactive approach not only identifies potential gaps in defenses but also equips security teams with actionable insights to enhance their incident response strategies. Continuous validation ensures that defenses are resilient against evolving threats, thereby strengthening overall cybersecurity posture.
Key Takeaways
- The XMRig wormable campaign employs advanced techniques like BYOVD and time-based logic bombs.
- A comprehensive understanding of attack timelines aids in quicker incident response.
- Regular updates and user education are crucial in defending against cryptojacking threats.
- Monitoring resource usage is vital for early detection of cryptojacking activities.
Frequently Asked Questions
What is cryptojacking?
Cryptojacking is a form of cyber attack where unauthorized parties utilize a victim’s computing resources to mine cryptocurrencies without their consent, leading to degraded system performance and increased costs.
How can I detect if my system is being used for cryptojacking?
Indicators include unexpected slowdowns, elevated CPU usage, and increased system temperatures. Utilizing monitoring tools can help identify these unusual activities early.
What are BYOVD exploits?
The BYOVD exploit involves leveraging existing vulnerable drivers on a system to execute malicious payloads, allowing attackers to bypass security measures effectively.
