# MAL-2026-10991: Malicious code in make-helper (PyPI)


- **Type:** Malicious package
- **Package:** `make-helper` (PyPI)
- **Published:** 22 Jul 2026

## What is MAL-2026-10991?

MAL-2026-10991 is a malicious package in make-helper, published on 22 Jul 2026. 

### Official description

On `import dev_helper`, the package's __init__.py starts a daemon thread that runs decryptor.decrypt_and_run(): it fetches an AES-GCM key from the hardcoded endpoint https://key-2qfm.vercel.app/api/key, decrypts the shipped dev_helper/encrypted.bin (16.9 KB ciphertext, nonce prepended), and executes the plaintext via exec(plaintext, {'__name__': '__main__'}). The auto-start is gated to skip interactive Python sessions and PYTHONSTARTUP contexts, so the payload fires in CI and production imports but stays hidden from REPL inspection. Logging is disabled (logging.disable(logging.CRITICAL)) and errors are swallowed. The package's stated purpose ("a helpful developer utility") does not disclose any of this, and the true payload is opaque without the remote key, allowing the operator of key-2qfm.vercel.app to rotate the executed code at will.

The package embeds encrypted code that, during import, is decrypted using an externally sourced password. The recovered code is executed and starts a bot capable of exfiltrating local files.

---

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

Campaign: 2026-07-make-helper

Reasons (based on the campaign):

 - files-exfiltration

 - obfuscation

 - uses-telegram-bot

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

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

## Sources

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

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