# MAL-2026-10978: Malicious code in reimagined-broccoli (PyPI)


- **Type:** Malicious package
- **Package:** `reimagined-broccoli` (PyPI)
- **Published:** 21 Jul 2026

## What is MAL-2026-10978?

MAL-2026-10978 is a malicious package in reimagined-broccoli, published on 21 Jul 2026. 

### Official description

The package `reimagined-broccoli` ships a benign-looking stub at `reimagined_broccoli/main.py` that only prints a success message. The tarball also ships `redis.zip` (declared in MANIFEST.in), which contains a second `main.py`, an opaque native ELF `redis.so`, and a `.env`. The package exposes a single console-script `reimagined-broccoli` whose entry point runs `start.sh`, which executes `unzip -o "$SCRIPT_DIR/redis.zip"` — overwriting the shipped stub — and then `python3 "$SCRIPT_DIR/main.py"`, invoking the extracted payload alongside `redis.so`. There is no hash or signature verification of the archive contents. The package metadata is placeholder (`Your Name`, an auto-generated repository slug) and the file name `redis.so` does not correspond to the Redis project. The visible Python source is a decoy; the code actually executed on CLI invocation is the opaque bundled binary/script pair inside the archive. This is the extract-overwrite-execute dropper shape carrying an unverifiable native payload from a placeholder-author publisher.

In this campaign, packages use names similar to popular services (e.g. Kimi AI) to deploy cryptominer.

---

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

Campaign: 2026-07-kimichat

Reasons (based on the campaign):

 - cryptominer

## What should I do about MAL-2026-10978?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10978 is a malicious package: reimagined-broccoli (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10978/ (Markdown: https://insights.sbomify.com/MAL-2026-10978/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10978

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10978/
Summaries are generated and may contain mistakes; the official description above is the record.