Which versions of cas-base are malicious?

The following PyPI versions of cas-base are flagged malicious: 1.5.2, 1.5.3, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.5, 1.6.6, 1.6.9, 1.7.1. Treat any of these as compromised.

How do I remediate cas-base if I installed it?

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

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

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

Malicious package

cas-basePyPI

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

MAL-2025-193014

Immediate action

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

pip uninstall cas-base

What this malware does

The package contains code to install remotely stored malware and ensure its persistence. The code is not triggered automatically; it requires a separate trigger.

Originally, cas-base was detected in 2025-07 with an unclear payload. Later it got updated to a clearly malicious payload

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

Campaign: 2025-07-cas-base

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
persistence

Malicious versions

15 flagged

1.5.21.5.31.5.51.5.61.5.71.5.81.5.91.6.01.6.11.6.21.6.31.6.51.6.61.6.91.7.1

Indicators of compromise (SHA-256)

69eb341218878aebdec66eb5a44391314921fe3c7fb387021d0684bbb91913b3

ebe4dad19c45d7bacbd4a1a3de525d0117559fa90434ca71f38160072a539a58

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 cas-base (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cas-base across your stack and pipelines.
If you installed it — respond
cas-base 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 cas-base 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 cas-base 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. cas-base on PyPI has been identified as a malicious package (versions 1.5.2, 1.5.3, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.6.0, and 7 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-cas-base

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks cas-base-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