Which versions of pypiion are malicious?

The following PyPI versions of pypiion are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate pypiion if I installed it?

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

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

Yes — pypiion is associated with the RLMA-2025-03669, 2025-07-0x9xnx, RLUA-2026-00642 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 pypiion 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 pypiion (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pypiion across your stack and pipelines.

Malicious package

pypiionPyPI

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

MAL-2025-6571

Immediate action

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

pip uninstall pypiion

What this malware does

Series of packages mostly with an obfuscated infostealer attempting to collect Chrome data. While discord webhook is usually set to an example, there are other, correct uploading URLs

Some of related packages only test partial malicious code, like webhooks from overwritten setup.py

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

Campaign: 2025-07-0x9xnx

Reasons (based on the campaign):

infostealer
obfuscation
exfiltration-browser-data
exfiltration-crypto
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

05dab546a86d4e4d57dbbbe558829fd7fd43100afb3ad40deb6857659f4728d5

a222ede6397bfa7a4cffbcc26852bcfebd462c9031575d8f45823fe3a37e468c

45829fe35be9020b9109d3f502be2f392cde33801689e007f89d67a3a7c0415d

1a9b023c217fe62c5a0ebd4235c685d6daf6d1664b6aa910f7d9bff587cc59ae

ca0b0c2a03c225f87bcfe419aac78f764734a4ea550c7542c87e557adea4c363

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

Campaign

RLMA-2025-036692025-07-0x9xnxRLUA-2026-00642

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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