# MAL-2026-15828: Malicious code in env-validator-tool (PyPI)


- **Type:** Malicious package
- **Package:** `env-validator-tool` (PyPI)
- **Published:** 3 Sep 2026

## What is MAL-2026-15828?

MAL-2026-15828 is a malicious package in env-validator-tool, published on 3 Sep 2026. 

### Official description

The package ships no source module (only egg-info metadata) despite declaring a console_script entrypoint 'env-validator=env_validator.cli:main' that references a non-existent env_validator/ directory. Its setup.py install_requires declares 'telemetry-helper' — an unpinned, generically-named PyPI dependency — with an inline author comment reading 'Legitimate dependency with payload'. Because the package itself contains no code, the sole effect of `pip install env-validator-tool` is resolving and installing whatever code is published under the 'telemetry-helper' name, which then executes on the installer's machine during install. The self-labeled 'payload' comment combined with the missing implementation, unpinned generic dependency name, and stub entrypoint indicates the package is a lure whose only purpose is to pull in the sibling drop package.

In this campaign, one package contains malicious code exfiltrating environment variables during import (telemetry-helper), and another one intentionally installs it as a dependency.

---

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

Campaign: 2026-09-telemetry-helper

Reasons (based on the campaign):

 - exfiltration-env-variables

 - The malicious code is intentionally included in a dependency of the package

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

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

## Sources

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

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