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 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 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?

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

Malicious package

PirxcyPackagePyPI

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

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