# MAL-2026-6289: Malicious code in equest (PyPI)


- **Type:** Malicious package
- **Package:** `equest` (PyPI)
- **Published:** 23 Jun 2026

## What is MAL-2026-6289?

MAL-2026-6289 is a malicious package in equest, published on 23 Jun 2026. 

### Official description

The package name `equest` is a one-character deletion of the widely-used `requests` package and ships no functional library code. setup.py registers custom install and egg_info cmdclasses so that on `pip install` or `pip download`, the package collects the full process environment (`os.environ` serialized as `key=value` pairs) and the output of `ps -elf`, then POSTs both to `http://gjampdwmdjmppwedtkpbbdkq05f6iiz6r.oast.fun` via curl over plaintext HTTP. The destination is an Interactsh (oast.fun) collector subdomain controlled by the publisher. Any CI/build secrets present in the installer's environment at install time (cloud credentials, registry tokens, GitHub tokens, database credentials) are leaked to the attacker, and the running process list reveals additional host context. The README self-describes the package as a proof-of-concept of arbitrary code execution via `pip install`.

During installation, the package exfiltrates env variables

---

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

Campaign: 2026-06-ip-rotat

Reasons (based on the campaign):

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

 - exfiltration-env-variables

 - typosquatting

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

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

## Sources

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

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