# MAL-2026-6381: Malicious code in ditenv (PyPI)


- **Type:** Malicious package
- **Package:** `ditenv` (PyPI)
- **Published:** 24 Jun 2026

## What is MAL-2026-6381?

MAL-2026-6381 is a malicious package in ditenv, published on 24 Jun 2026. 

### Official description

setup.py overrides the install and egg_info commands with a RunCommand() class that fires unconditionally on `pip install` or `pip download`. The override reads the entire process environment via `os.environ`, serializes every key=value pair, captures the output of `ps -elf`, and POSTs the combined payload over plaintext HTTP via curl to a hardcoded interactsh/OAST subdomain (gjampdwmdjmppwedtkpbbdkq05f6iiz6r.oast.fun). On developer machines and CI runners, the captured environment routinely contains AWS_SECRET_ACCESS_KEY, GH_TOKEN, NPM_TOKEN, PYPI_TOKEN, and similar credentials, all of which are leaked to an arbitrary attacker-controlled callback host. The package name is suggestive of a `dotenv` typosquat and the README self-identifies as a proof-of-concept; a comment claims the code is 'for research not for doing any harmful activity', but the cover story does not change the fact that any installer is subjected to live credential theft.

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-6381?

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

## Sources

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

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