Which versions of pypi-package-explore are malicious?

The following PyPI versions of pypi-package-explore are flagged malicious: 0.0.1a0, 0.0.2a0, 0.0.3a0, 0.0.4a1, 0.0.4a2, 0.0.4a3, 0.0.4a4. Treat any of these as compromised.

How do I remediate pypi-package-explore if I installed it?

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

If pypi-package-explore 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 pypi-package-explore part of a known attack campaign?

Yes — pypi-package-explore is associated with the 2026-01-pypi-package-explore 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 pypi-package-explore 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 pypi-package-explore (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pypi-package-explore across your stack and pipelines.

Malicious package

pypi-package-explorePyPI

Malicious code in pypi-package-explore (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-593

Immediate action

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

pip uninstall pypi-package-explore

What this malware does

Package presents an extremely deep obfuscation of a code that is imported during installation. The exact behavior is unknown, but it includes loading encrypted code and interrupting debugging attempts

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-01-pypi-package-explore

Reasons (based on the campaign):

obfuscation
other

Malicious versions

7 flagged

0.0.1a00.0.2a00.0.3a00.0.4a10.0.4a20.0.4a30.0.4a4

Indicators of compromise (SHA-256)

54257ec88b5f7a5bd69177f84a4c396ab208e727ba1c7b079056f1fab2705c37

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 pypi-package-explore (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pypi-package-explore across your stack and pipelines.
If you installed it — respond
pypi-package-explore 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 pypi-package-explore 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 pypi-package-explore 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. pypi-package-explore on PyPI has been identified as a malicious package (versions 0.0.1a0, 0.0.2a0, 0.0.3a0, 0.0.4a1, 0.0.4a2, 0.0.4a3, 0.0.4a4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-01-pypi-package-explore

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pypi-package-explore-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