Which versions of coloreasyprint are malicious?

The following PyPI versions of coloreasyprint are flagged malicious: 0.4.7.dev1, 0.4.7.dev2, 0.4.7.dev3. Treat any of these as compromised.

How do I remediate coloreasyprint if I installed it?

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

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

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

Malicious package

coloreasyprintPyPI

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

MAL-2026-3127

Immediate action

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

pip uninstall coloreasyprint

What this malware does

During import, the code downloads and executes encrypted payload from remote location. During analysis, remote code was prepared to download the next stage executable. This is likely selectively delivered to victims as the code polls the C2 server periodically with the local hostname and awaits the next stage to download.

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

Campaign: 2026-04-pathjoin

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

0.4.7.dev10.4.7.dev20.4.7.dev3

Indicators of compromise (SHA-256)

d52af876a91a6ff5ff8144b705201fd465db94ad89f0e1b37bd22fe6ca0f5622

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

Campaign

2026-04-pathjoin

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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