Which versions of cubesat-upstream-driver are malicious?

The following PyPI versions of cubesat-upstream-driver are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate cubesat-upstream-driver if I installed it?

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

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

Yes — cubesat-upstream-driver is associated with the 2026-08-cubesat-upstream-driver, IN-MAL-2026-017205 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 cubesat-upstream-driver across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cubesat-upstream-driver (version 1.0.1).

Malicious package

cubesat-upstream-driverPyPI

Advisory published Aug 9, 2026Updated Aug 10, 2026

cubesat-upstream-driver is a confirmed malicious PyPI package (MAL-2026-13666) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cubesat-upstream-driver (PyPI)

MAL-2026-13666

Immediate action

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

pip uninstall cubesat-upstream-driver

What this malware does

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

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

d669fdf7584f17d952cec3ed432bdb8f07672b43c3bc42ae68aa2d042d51481b

1f5f2cf32e29ec0daedda5112ca2c560e69b4c4cd77850d6dc52d7a448e343a2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cubesat-upstream-driver (version 1.0.1).
If you installed it — respond
cubesat-upstream-driver 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 cubesat-upstream-driver 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. cubesat-upstream-driver on PyPI has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-cubesat-upstream-driverIN-MAL-2026-017205

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks cubesat-upstream-driver-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

Explore

All malware advisories How O3 detects malware Vulnerability database