Which versions of enhancer are malicious?

The following PyPI versions of enhancer are flagged malicious: 0.2.3. Treat any of these as compromised.

How do I remediate enhancer if I installed it?

enhancer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed enhancer — how do I know if it already compromised me?

If enhancer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is enhancer part of a known attack campaign?

Yes — enhancer is associated with the IN-MAL-2026-002222 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find enhancer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for enhancer (version 0.2.3).

Malicious package

enhancerPyPI

Advisory published May 12, 2026Updated May 13, 2026

enhancer is a confirmed malicious PyPI package (MAL-2026-3691) that steals credentials and exfiltrates sensitive data (malicious version 0.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in enhancer (PyPI)

MAL-2026-3691

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall enhancer

What this malware does

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.

Malicious versions

1 flagged

0.2.3

Indicators of compromise (SHA-256)

cefeea627aa1a0cc84aeedff1db0ae88ebf61b233bb9b20fa82b0a5fd0737cbf

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for enhancer (version 0.2.3).
If you installed it — respond
enhancer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If enhancer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. enhancer on PyPI has been identified as a malicious package (version 0.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002222

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks enhancer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database