Which versions of canvas-crawler are malicious?

The following PyPI versions of canvas-crawler are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate canvas-crawler if I installed it?

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

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

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

Malicious package

canvas-crawlerPyPI

Malicious code in canvas-crawler (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2943

Immediate action

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

pip uninstall canvas-crawler

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

1 flagged

0.1

Indicators of compromise (SHA-256)

c5b99cbc1e7a1473d7e6c905c0a9d113a2cd4529d5a90fa0debc679154c952f7

41c83dd2ff5980165d0259fbc26b0b0d3d0a02d9e5041ca962273e4cca43537e

e26aa849df7710714fbcef97638e99ec2f03a138b1e27c78ad0bb2caff64d5e1

0cc0eaf8ba06a81e4c4af1ea1fb736306b558888f7d132f6d54de65a6d0e3917

2451b0eae84085328bfbbef2ffab95b0f9be136f79c632006753200337cf2217

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

Campaign

RLMA-2025-01941GENERIC-standard-pypi-install-pentestRLUA-2026-00178

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks canvas-crawler-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