Which versions of PirxcyPackage are malicious?

The following PyPI versions of PirxcyPackage are flagged malicious: 8.0.0. Treat any of these as compromised.

How do I remediate PirxcyPackage if I installed it?

Remove PirxcyPackage from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — PirxcyPackage is associated with the IN-MAL-2026-002316 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 PirxcyPackage across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for PirxcyPackage (version 8.0.0).

Malicious package

PirxcyPackagePyPI

Advisory published May 12, 2026Updated May 13, 2026

PirxcyPackage is a confirmed malicious PyPI package (MAL-2026-3695) that executes malicious code on install (malicious version 8.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pirxcypackage (PyPI)

MAL-2026-3695

Immediate action

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

pip uninstall PirxcyPackage

What this malware does

PirxcyPackage/init.py fetches https://pastebin.com/raw/91tFF63S and passes the response body to exec() on every import. This is a textbook remote-code-execution supply-chain pattern: the payload is mutable, unauthenticated, unsigned, and controlled by a third-party paste owner, so any installer importing this package runs arbitrary attacker-chosen Python. The staging via Pastebin also ensures static review of the wheel cannot observe actual behavior. Installer harm is direct and unambiguous.

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

5de481a31a831804a096bf6cf87157c0b0ee158aa7306c95080447764f9f7540

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for PirxcyPackage (version 8.0.0).
If you installed it — respond
Remove PirxcyPackage from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If PirxcyPackage 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. PirxcyPackage on PyPI has been identified as a malicious package (version 8.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002316

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks PirxcyPackage-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database