Which versions of chain00x are malicious?

The following PyPI versions of chain00x are flagged malicious: 0.1, 0.2, 0.5, 0.6, 0.9, 1, 1.0. Treat any of these as compromised.

How do I remediate chain00x if I installed it?

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

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

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

Malicious package

chain00xPyPI

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

MAL-2024-11555

Immediate action

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

pip uninstall chain00x

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.50.60.911.0

Indicators of compromise (SHA-256)

a275349c0c0fa10c5e3d285925fdea490f33138befbf7412a8d7875743c72303

83795be7813d595fe57365d18882741f457977287ebc2c64ccb8602b8b2eb470

56ebf0633819f86071043ba5f849ae335481e8f606345b5441408cd4bf0c754d

a861a1b1fd666a56f3bd2d891aee1cfb5eccbea2e6fc2c6a49f3aaf85d53c69a

a33040f7c4319171644463079fc90e1893782ae584d157a1e9f40f1f4d4293ba

e0d593cc10a42ec3b5d60c70f91139027b615762c5e852025b8f81cee5b33d63

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

Campaign

RLMA-2024-11001GENERIC-standard-pypi-install-pentestRLUA-2026-00184

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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