Nanopool Claymore Dual Miner version 7.3 and earlier contains a remote code execution vulnerability in its miner API. According to the provided content, the issue can be abused to achieve remote code execution when the software is run with read/write mode enabled. The available information does not identify the specific vulnerable function or request handler, but indicates that the exposed API permits unsafe operations sufficient to execute attacker-controlled commands or code remotely under that configuration.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module targeting a remote code execution (RCE) vulnerability in the Nanopool Claymore Dual Miner software (CVE-2018-1000049). The exploit leverages the miner's remote manager API, which listens on TCP port 3333 by default, to upload and execute arbitrary files on both Windows and Linux systems. The module automatically detects the target platform and uses appropriate command stagers (PowerShell/VBS for Windows, shell/echo/printf for Linux) to deliver a payload, typically resulting in a remote shell. The exploit is fully weaponized, allowing the attacker to select and deliver any Metasploit payload. The module interacts with the miner's API using JSON-RPC requests to read configuration files and upload/execute scripts. The repository is structured as a single Ruby file compatible with the Metasploit framework, and is intended for use by penetration testers to demonstrate or leverage the vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.