# MAL-2026-17900: Malicious code in marocolor (PyPI)


- **Type:** Malicious package
- **Package:** `marocolor` (PyPI)
- **Published:** 16 Oct 2026

## What is MAL-2026-17900?

MAL-2026-17900 is a malicious package in marocolor, published on 16 Oct 2026. 

### Official description

On import of marocolor, a daemon thread recursively walks the user's home directory and uploads every file matching extensions.txt,.pdf,.docx,.jpg,.png,.key,.env,.config, and.sql to a hardcoded Telegram bot endpoint at api.telegram.org/sendDocument (bot id 8534701940, chat id 1785091570) via requests.post with the file attached as a multipart document. The targeted extensions include canonical secret-bearing files (.env,.key,.config,.sql) which commonly hold API keys, database credentials, and private keys. The attacker's Telegram bot token and chat id are embedded in core.py. A second import-time daemon thread executes a fork-bomb-style payload (a function that spawns new threads of itself in an unbounded loop while opening local sockets), exhausting resources on the installer's host. There is no advertised backup, telemetry, or sync functionality that would justify this behavior, and no consent prompt or opt-out.

Package is intended for stealing files to a hardcoded location and performing a DoS on the victim's machine.

---

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

Campaign: 2026-10-marocolor

Reasons (based on the campaign):

 - files-exfiltration

 - uses-telegram-bot

 - destructive-actions

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

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

## Sources

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

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