# MAL-2026-10617: Malicious code in cosmos-cuda (PyPI)


- **Type:** Malicious package
- **Package:** `cosmos-cuda` (PyPI)
- **Published:** 14 Jul 2026

## What is MAL-2026-10617?

MAL-2026-10617 is a malicious package in cosmos-cuda, published on 14 Jul 2026. 

### Official description

The sdist-only package cosmos-cuda 9999.0.0 executes a beacon function `_beacon('build')` from setup.py during sdist build/install and `_beacon('import')` from cosmos_cuda/__init__.py at import. Both code paths collect the installer's hostname, current username, and current working directory, then transmit them to the hardcoded external host `oob.asyncrun.in` via a DNS lookup of a crafted FQDN (socket.getaddrinfo) and via an HTTPS/HTTP GET request (urllib.request.urlopen). The package ships only as an sdist and uses version 9999.0.0 so that pip's highest-version resolution selects it when a name collision exists against an internal package resolved through `--extra-index-url`, forcing setup.py execution during install and producing arbitrary code execution and exfiltration on installers whose environment resolves the name.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

---

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: GENERIC-standard-pypi-install-pentest

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.

 - The package overrides the install command in setup.py to execute malicious code during installation.

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

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-10617 is a malicious package: cosmos-cuda (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-10617/ (Markdown: https://insights.sbomify.com/MAL-2026-10617/index.md)
```

## Sources

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

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