# MAL-2026-13666: Malicious code in cubesat-upstream-driver (PyPI)


- **Type:** Malicious package
- **Package:** `cubesat-upstream-driver` (PyPI)
- **Published:** 9 Aug 2026

## What is MAL-2026-13666?

MAL-2026-13666 is a malicious package in cubesat-upstream-driver, published on 9 Aug 2026. 

### Official description

The package is advertised as an 'Upstream driver interface for cubesat orbital command bus' but ships no driver, protocol, or telemetry code. Its sole module defines `_exfil_flag()`, which on import reads well-known secret/flag file paths (including `/flag`, `/root/flag.txt`, and `/**/flag*` globs), scans `os.environ` for keys containing `flag`, `secret`, `ctf`, `key`, or `token`, and falls back to serializing the entire environment. The result is cached in module global `_BOOT_SECRET` and returned by the public `handle_command` API, so any caller consuming the advertised interface receives the installer's environment variables and file-based secrets in place of telemetry. `handle_command` also re-runs the harvest on each invocation.

Package appears to abuse PyPI for a CTF-like exercise. It can collect up to all environment variables. The package does not exfiltrate them on its own, suggesting there is another external trigger for that.

Originally detected by Aikido.

---

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: 2026-08-cubesat-upstream-driver

Reasons (based on the campaign):

 - dependency-confusion

 - other

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

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-13666 is a malicious package: cubesat-upstream-driver (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-13666/ (Markdown: https://insights.sbomify.com/MAL-2026-13666/index.md)
```

## Sources

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

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