Which versions of cryptoaitools are malicious?

The following PyPI versions of cryptoaitools are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7. Treat any of these as compromised.

How do I remediate cryptoaitools if I installed it?

Remove cryptoaitools from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed cryptoaitools — how do I know if it already compromised me?

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

Yes — cryptoaitools is associated with the RLMA-2024-08074, RLUA-2024-11014 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 cryptoaitools across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cryptoaitools (7 malicious versions).

Malicious package

cryptoaitoolsPyPI

cryptoaitools is a confirmed malicious PyPI package (MAL-2024-9964) that executes malicious code on install (malicious versions 0.1, 0.2, 0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptoaitools (PyPI)

MAL-2024-9964

Immediate action

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

pip uninstall cryptoaitools

Malicious versions

7 flagged

0.10.20.30.40.50.60.7

Indicators of compromise (SHA-256)

52e9f8b83b661c35d7d79e3ad6c9f374a1dd580961a9e850b85b769635073772

b40e0895975a41256b831ed8749a3a2663cc2d18dee93f70518012f58ca7d7ef

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cryptoaitools (7 malicious versions).
If you installed it — respond
Remove cryptoaitools from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cryptoaitools 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. cryptoaitools on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-08074RLUA-2024-11014

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks cryptoaitools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database