Which versions of crayrandomiz are malicious?

The following PyPI versions of crayrandomiz are flagged malicious: 1.0.0, 1.0.1, 2.0.0. Treat any of these as compromised.

How do I remediate crayrandomiz if I installed it?

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

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

Yes — crayrandomiz is associated with the 2026-05-crayrandomiz 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 crayrandomiz across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for crayrandomiz (3 malicious versions).

Malicious package

crayrandomizPyPI

Advisory published May 7, 2026Updated May 8, 2026

crayrandomiz is a confirmed malicious PyPI package (MAL-2026-3367) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crayrandomiz (PyPI)

MAL-2026-3367

Immediate action

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

pip uninstall crayrandomiz

What this malware does

Package exfiltrates screenshots and network information to a hardcoded target.

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

Campaign: 2026-05-crayrandomiz

Reasons (based on the campaign):

spyware-like
exfiltration-generic
obfuscation

Malicious versions

3 flagged

1.0.01.0.12.0.0

Indicators of compromise (SHA-256)

70d147758fe5288bee2adc712e45b7836211b83ce0b209fd42a31e4b3696bbf2

a02f8c548a8b98554453e11fe917d096b013457d10602db42b791f0dca62deed

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-crayrandomiz

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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