Which versions of marocolor are malicious?

The following PyPI versions of marocolor are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate marocolor if I installed it?

marocolor 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 marocolor — how do I know if it already compromised me?

If marocolor 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 marocolor part of a known attack campaign?

Yes — marocolor is associated with the 2026-10-marocolor, IN-MAL-2026-021507 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 marocolor across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for marocolor (version 1.0.0).

Malicious package

marocolorPyPI

Advisory published Oct 16, 2026Updated Oct 16, 2026

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

Malicious code in marocolor (PyPI)

MAL-2026-17900

Immediate action

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

pip uninstall marocolor

What this malware does

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

38b0fa2ee77af46ad9daf78c024a0f599fd0798eef7605cb3eed50d8db65fa22

84922797997d30794d088ec8c54962534316449b26815c1fe4001bf2d3232bc2

8206a6d3278ef99ffe6f33a695ca3dd6b4ed9856912d79f3066a375d95bcd509

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for marocolor (version 1.0.0).
If you installed it — respond
marocolor 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 marocolor 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. marocolor on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-marocolorIN-MAL-2026-021507

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks marocolor-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