Which versions of voxcpmui4 are malicious?

The following PyPI versions of voxcpmui4 are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate voxcpmui4 if I installed it?

voxcpmui4 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.

I already installed voxcpmui4 — how do I know if it already compromised me?

If voxcpmui4 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.

Is voxcpmui4 part of a known attack campaign?

Yes — voxcpmui4 is associated with the 2026-10-voxeval campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find voxcpmui4 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for voxcpmui4 (version 0.2.0).

Part of a larger attack: 2026-10-voxeval published 11 malicious packages. See the full campaign →

Malicious package

voxcpmui4PyPI

Advisory published Oct 3, 2026Updated Oct 3, 2026

voxcpmui4 is a confirmed malicious PyPI package (MAL-2026-17467) that steals credentials and exfiltrates sensitive data (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in voxcpmui4 (PyPI)

MAL-2026-17467

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall voxcpmui4

What this malware does

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

1 flagged

0.2.0

Indicators of compromise (SHA-256)

c0f6ddfc6a324d42219bbea8405be17115f83eca0e2d2eecb4e3fe6b6ec3dbde

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for voxcpmui4 (version 0.2.0).
If you installed it — respond
voxcpmui4 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 voxcpmui4 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

No. voxcpmui4 on PyPI has been identified as a malicious package (version 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-voxeval

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks voxcpmui4-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database