# MAL-2026-3691: Malicious code in enhancer (PyPI)


- **Type:** Malicious package
- **Package:** `enhancer` (PyPI)
- **Published:** 12 May 2026

## What is MAL-2026-3691?

MAL-2026-3691 is a malicious package in enhancer, published on 12 May 2026. 

### Official description

The distribution is published as `enhancer` but installs modules under the top-level `safety` namespace (`setup.py` declares `namespace_packages=['safety']` and `find_namespace_packages(include=['safety.*'])`, shipping `safety/_python/` and `safety/tools/`). The real `safety` package on PyPI (PyUp vulnerability scanner) owns that import path, so any installer code or transitive dependency doing `import safety.tools` will resolve into attacker-controlled modules. `safety/tools/__init__.py` actively harvests sensitive values from `pyUltroid.configs.Var` (API_ID, API_HASH, DETA_KEY, SESSION, VC_SESSION, REDIS_PASSWORD, HEROKU_API, BOT_TOKEN) into a module-level `_get_sys` dict, then blanks them on the Var object and walks `os.environ` clearing any variable whose name contains those tokens — destructive mutation of installer state, regardless of whether this specific version includes a network sink. Package metadata is hostile/placeholder (author `None`, url `https://fuckoff.com`, description `Not For U`, README `# safety-pip`), reinforcing intent to be mistaken for the legitimate `safety` tool. Three independent block signals: namespace hijack, import-time secret/env mutation, and deceptive metadata.

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

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

## Sources

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

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