Which versions of crowdstrike-foundry are malicious?

The following PyPI versions of crowdstrike-foundry are flagged malicious: 20.1.0, 20.2.0, 20.3.0. Treat any of these as compromised.

How do I remediate crowdstrike-foundry if I installed it?

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

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

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

Malicious package

crowdstrike-foundryPyPI

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

MAL-2025-912

Immediate action

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

pip uninstall crowdstrike-foundry

What this malware does

The package looks like a beginning for a further work. In fact, the uploader has shortly published a few similar packages appearing to be e.g. an integration for a known application, but containing only a "telemetry" module exfiltrating basic info about the user. This package has no other purpose than collecting data about users. In addition, it appears to be largely generated by an LLM.

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: 2024-12- sajansubedi

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.
dependency-confusion

Malicious versions

3 flagged

20.1.020.2.020.3.0

Indicators of compromise (SHA-256)

9d893ee2474d088e1ae19c166965108edfd1c895c7bf66ced4eb1c294277581f

a3dcd3cc4cc3a9ef95cdfd0522e8fa71f21a4bc515d04cec33b2ca44ee9020cb

89a436ce955b3eb01df1e23a27f7b9d0091b3720818f31559038c7af44bca276

6d8329930e185e008a282aa1e8b997e2a9000ff472bf89c06df1f55c80a1861a

b9c0a0a111f535ec39536e98cfb7bcda8d853ce9e4e1aa0c703cdd324a605282

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

Campaign

RLMA-2025-004512024-12- sajansubediRLUA-2026-00229

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks crowdstrike-foundry-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