Which versions of pycolorlib001 are malicious?

The following PyPI versions of pycolorlib001 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pycolorlib001 if I installed it?

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

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

Yes — pycolorlib001 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 pycolorlib001 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 pycolorlib001 (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycolorlib001 across your stack and pipelines.

Malicious package

pycolorlib001PyPI

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

MAL-2026-3042

Immediate action

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

pip uninstall pycolorlib001

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d13044c47d5f0b928df9bb3c300bbb520cef7df9cc929b859e7f2edd67d8221f

dacf9f2f48bb38c32b613ccae88a30efddbef777e9a9fd30f7d289dabf03b3a0

9a69bd219c6c5fbcffcd3aae3165939e3aa73a3cc73d822b10bc4925964ce53c

936547b0e2d0c52645ea79e64bcc357a7a1ce8b589438899106aeb691d33e048

5524208ddb140d92de67fc9bf0e794660548cce12b1b0670ee5b832d0b8b1148

79ccf3d857ae0bf82c72ac296ac5ab3d9adec0a0c86ba65077f5fb02780851dc

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 pycolorlib001 (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycolorlib001 across your stack and pipelines.
If you installed it — respond
pycolorlib001 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 pycolorlib001 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 pycolorlib001 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. pycolorlib001 on PyPI has been identified as a malicious package (version 0.0.1 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) · reporter

Detect & block this

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