Which versions of voto3 are malicious?

The following PyPI versions of voto3 are flagged malicious: 0.1, 0.2, 0.2.0, 0.3, 0.3.0, 0.7.0, 0.9.0. Treat any of these as compromised.

How do I remediate voto3 if I installed it?

voto3 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 voto3 — how do I know if it already compromised me?

If voto3 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is voto3 part of a known attack campaign?

Yes — voto3 is associated with the RLMA-2024-11207, GENERIC-standard-pypi-install-pentest, RLUA-2026-00895 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 voto3 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for voto3 (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging voto3 across your stack and pipelines.

Malicious package

voto3PyPI

Malicious code in voto3 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11746

Immediate action

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

pip uninstall voto3

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

7 flagged

0.10.20.2.00.30.3.00.7.00.9.0

Indicators of compromise (SHA-256)

c9e1a3c25c8f9475f578e6bafa5f1b1848a72f07650086fc62cd657fe7b198df

81a68f30b26e8401be12d400e10ce1495f4a80c43b6db5da8c59e2d323e911f1

34f516638c010eaffd4b7bf199d71925e9963e438cd619739347a6d0ac4bb6be

3e2fc58543015336c36609305ad1216238773d6533bd689f15c830025b1d3536

e300feb7298d224d52a3c1c885ef3f386b7acecaeac3604205d7d877b21179da

19b45df695c84ac36c978e1b64ebb33af520d2e5c50274ad1e7ecd029c3fe2e9

a4ebfa6a9372c6d9a1760b86d21373cc8aa46c9296072d18abaeeb1df1bcbdee

a81ee11c866c958196916b43fb34ae7477affde50e22f5a6e6a24f4beb76d37e

41cd87da95a7ff9fe885a37749b315e94a5d40315926df9fd428f2ccce79f5f9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for voto3 (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging voto3 across your stack and pipelines.
If you installed it — respond
voto3 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 voto3 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks voto3 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. voto3 on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.2.0, 0.3, 0.3.0, 0.7.0, 0.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11207GENERIC-standard-pypi-install-pentestRLUA-2026-00895

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks voto3-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