Which versions of aiolrucache are malicious?

The following PyPI versions of aiolrucache are flagged malicious: 0.1.0, 0.1.1, 0.2.0, 0.3.0. Treat any of these as compromised.

How do I remediate aiolrucache if I installed it?

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

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

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

Search your lockfiles and build artifacts for aiolrucache (4 malicious versions).

Malicious package

aiolrucachePyPI

Advisory published Mar 21, 2026Updated Mar 21, 2026

aiolrucache is a confirmed malicious PyPI package (MAL-2026-2020) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiolrucache (PyPI)

MAL-2026-2020

Immediate action

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

pip uninstall aiolrucache

What this malware does

The package masquerades as a utility, but during import, code loads obfuscated modules with RAT- and spyware-like functionality, including: exfiltrating files, executing remote code, taking screenshots, monitoring and exfiltrating the clipboard content. Malicious code is controlled via Discord.

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

Campaign: 2026-03-aiolrucache

Reasons (based on the campaign):

rat
spyware-like
keylogger
clipboard-stealing
obfuscation
files-exfiltration

Malicious versions

4 flagged

0.1.00.1.10.2.00.3.0

Indicators of compromise (SHA-256)

8b847ab6789b3a3848d887f76adae74d05523dd4cb1a974372518679d27ed70e

Detection & response playbook

Credential / info stealer

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

Campaign

2026-03-aiolrucache

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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