Which versions of foop are malicious?

The following PyPI versions of foop are flagged malicious: 60.0.0. Treat any of these as compromised.

How do I remediate foop if I installed it?

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

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

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

Malicious package

foopPyPI

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

MAL-2025-927

Immediate action

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

pip uninstall foop

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

1 flagged

60.0.0

Indicators of compromise (SHA-256)

e61a1273aa0ad7ea095ba7550f9892016019cd0181ea839b9bcaf8d8e3a8e26e

3b7141c12540ac3522c0867324eca89b6b91deca141f9f5369b00482e30ae612

8dd063ab676114f4458052dd442285fb78dace9c91fd0b810c5c137cf3a4cb44

9ae4b442a3089450b91b5053bbd553625386e13c80ac60ae7ea7cd61e7f06973

5d04c0cb65cac6f36427a095d22b797b9d7ee2df03bd594ba67c8b901079aa44

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

Campaign

RLMA-2025-004662024-12- sajansubediRLUA-2026-00331

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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