Which versions of xxx-bale are malicious?

The following PyPI versions of xxx-bale are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate xxx-bale if I installed it?

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

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

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

Malicious package

xxx-balePyPI

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

MAL-2026-3428

Immediate action

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

pip uninstall xxx-bale

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.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1109b5dc74c94551027044e54e20f9c1c18f89d53da6af87861ba4773eae1966

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