enhancer

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (cefeea627aa1a0cc84aeedff1db0ae88ebf61b233bb9b20fa82b0a5fd0737cbf)
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.

Compromised versions (1)

• 0.2.3

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.