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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crayrandomiz (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crayrandomiz across your stack and pipelines.

Malicious package

crayrandomizPyPI

Malicious code in crayrandomiz (PyPI) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for crayrandomiz (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging crayrandomiz across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks crayrandomiz before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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