Which versions of cpan are malicious?

The following PyPI versions of cpan are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate cpan if I installed it?

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

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

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

Malicious package

cpanPyPI

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

MAL-2025-6483

Immediate action

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

pip uninstall cpan

What this malware does

Installing the package starts a revshell and download and starts a remote script (depending on version, different malicious functionality). The name seems to imitate CPAN.org

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

Campaign: 2025-06-cpan

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
impersonation
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

bd1681dc89631934bce508a308d2c708603f6d09ca9cb6efbe90f4b33d1cbaea

7d1167d235aa8d1bfa384247116621d8a00d34455aabf31bc8f46e5f348ae7b2

e70433969aea3c8283f99098b25b8a598f427b5fd451e9bfd5bc46098704bfb2

58814925612b24ead324b54f764c54aea2512fe1a85e1ba3fd152395a2acaa93

4b423c9367571c3f7f63f1df132ff76424ff0cebb455a95d212c659dac56bbb8

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

Campaign

RLMA-2025-035742025-06-cpanRLUA-2026-00226

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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