voxevalPyPI
Advisory published Updated
voxeval is a confirmed malicious PyPI package (MAL-2026-17457) that steals credentials and exfiltrates sensitive data (malicious versions 0.4.2, 0.4.3, 0.4.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in voxeval (PyPI)
What this malware does
The package advertises itself as a TTS evaluation harness but ships two large bundled binaries and executes them on the installer's host. voxeval/bin/voxtts-core is an ~8MB ELF launched with an XMRig-shaped configuration (pools, donate-level, print-time, huge-pages, cpu.threads, user=run_id, pass="vox") pointing at a hardcoded Monero pool at 185.194.177.249:443. The pool host is split into two base64 chunks (MTg1LjE5NA==, MTc3LjI0OQ==) and reassembled at runtime, and configuration keys are string-concatenated ("po"+"ools", "--"+"config=") to defeat literal keyword scans. A second bundled binary, a ~40MB cloudflared, is invoked as cloudflared access tcp --hostname <edge> --url 127.0.0.1:<port> --no-autoupdate to proxy the miner's egress through Cloudflare's edge and evade DNS/IP-based blocking of the pool. A _Progress helper fabricates fake training-progress lines (step N/250000 loss=... tok/s=...) so the miner's output resembles ML training in notebook logs. The dropper chmods the core binary to 0o755 and spawns it via Popen. Installing or invoking voxeval causes sustained CPU consumption on the installer's host for the benefit of the attacker's mining wallet, with egress deliberately obscured.
The package imitates real activity and instead deploys a coin miner.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-10-voxeval
Reasons (based on the campaign):
- cryptominer
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for voxeval (4 malicious versions).
If you installed it — respond
voxeval is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If voxeval was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks voxeval-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.