Loading vulnerability…
The Energizer DUO USB battery charger software installs UsbCharger.dll, which in turn drops Arucer.dll into the %WINDIR%\system32 directory. Arucer.dll opens a backdoor on TCP port 7777, allowing remote attackers to download and execute arbitrary programs on the affected Windows system. This backdoor is hardcoded and does not require authentication, providing attackers with full remote code execution capabilities.
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 systems infected with the Arucer.dll trojan, which was distributed with the Energizer DUO USB battery charger software. The exploit connects to the backdoor installed by the trojan, which listens on TCP port 7777, and uploads a user-specified executable payload to a random file in the C:\ directory. It then instructs the backdoor to execute the uploaded payload, enabling arbitrary code execution on the compromised Windows system. The module leverages Metasploit's payload generation and is fully weaponized, allowing the operator to select any compatible payload. The main fingerprintable endpoints are the TCP port 7777 (used by the backdoor) and the file path on the target system where the payload is written and executed. The code is structured as a standard Metasploit exploit module, with clear separation of command encoding, payload upload, and execution logic.
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.
1 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.