Which versions of pycolorlib3 are malicious?

The following PyPI versions of pycolorlib3 are flagged malicious: 0.0.4, 0.0.5. Treat any of these as compromised.

How do I remediate pycolorlib3 if I installed it?

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

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

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

Malicious package

pycolorlib3PyPI

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

MAL-2026-2433

Immediate action

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

pip uninstall pycolorlib3

What this malware does

During installation package downloads and runs a malicious executable. Likely continuation of 2026-03-rowrap.

The campaign is built over a malicious Roblox API wrapper. The roboat[.]pro (later robase[.]app) domain advertises a wrapper that is either directly malicious (as roboat collected in the campaign 2026-03-rowrap) or uses a malicious dependencies (like roboat-utils). New versions are published simultaneously with malicious dependencies and quickly removed. Another advertisement channel is https://github.com/Addi9000/roboat referencing two active contributors: https://github.com/Addi9000 and https://github.com/RoCruise

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

Campaign: 2026-03-roboat-addition

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
malware
clones-real-package

Malicious versions

2 flagged

0.0.40.0.5

Indicators of compromise (SHA-256)

a239d96bd3d8ecc300c6f92ee9c1511f885a3ddd9cfae3a05ba30a39e2c2ac13

9f00afe251753c79c25e7028409f57e20dfafaefa4a530bd294dd4fdd038d851

ec41e05322e9de3a51cdc335be81e258ee16090b19b1742bdc60dc920c23cd2e

a68a3758a376ba30647309dc27c7f1b2b8d6930c160cc8ffa77e034465475b2e

3f7d9bf2d962932d8912712e20190b6c8ed7c0fc8860cc837219a7063e51aa64

d04486b87238ba6bdd7153a23ff1af258b646d057f58c5f02ca67c6324209f46

22c84d1bcfac7d68fb2db1c9610d281372db5e2ef93edb1a90903c6a6b772e6c

612c5dc34c77538fca2632ba590e02cc0c43a9cf893fbdd2e9e83a19ad6add24

108790447290c477f500a916de1b2dcd2b379f9b9d3a529fd18045332e50055b

75df964ceac921d7a6d2c2a296afc94ee99c3c7d8c4aa5abcd64e0a3c5303441

390bb754965afc6b7bb54cd88038bb382881f30fec7e8b23891bb940bfc8f395

acb3352c4f85e94d3a78163860e22c9af88cb29384564c3a62dcd3fda466e450

3955c630bcdef4b16aba0bea6808dafd8fc87f72a19a4fc7d30a8d8a6feeeb8c

a0ef1877c19765670a26a652dcd8760c415810d9476961b077cade0562ccc35a

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

Campaign

2026-03-roboat-addition

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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