Which versions of broccoli-server are malicious?

The following PyPI versions of broccoli-server are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate broccoli-server if I installed it?

Remove broccoli-server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed broccoli-server — how do I know if it already compromised me?

If broccoli-server was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is broccoli-server part of a known attack campaign?

Yes — broccoli-server is associated with the RLMA-2025-03553 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 broccoli-server across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for broccoli-server (version 0.0.1).

Malicious package

broccoli-serverPyPI

broccoli-server is a confirmed malicious PyPI package (MAL-2025-6468) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in broccoli-server (PyPI)

MAL-2025-6468

Immediate action

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

pip uninstall broccoli-server

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

df78ee42439d66163e48ecd0296a3249451bb5f7c2e3f4e0578fe2df45058824

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for broccoli-server (version 0.0.1).
If you installed it — respond
Remove broccoli-server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If broccoli-server was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. broccoli-server on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03553

Credits

ReversingLabs · finder

Detect & block this

O3 blocks broccoli-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database