Which versions of asciitoart are malicious?

The following PyPI versions of asciitoart are flagged malicious: 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate asciitoart if I installed it?

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

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

Yes — asciitoart is associated with the 2024-11-asn1tool 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 asciitoart across my projects, lockfiles, and CI pipelines?

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

Malicious package

asciitoartPyPI

Advisory published Apr 13, 2026Updated Apr 13, 2026

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

Malicious code in asciitoart (PyPI)

MAL-2026-2624

Immediate action

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

pip uninstall asciitoart

What this malware does

Through an obscure way, one of the package files got overwritten by a remote obfuscated code, which appears to be an infostealer. After executing the malicious code, the package covers the tracks by overwriting all relevant code files.

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

Campaign: 2024-11-asn1tool

Reasons (based on the campaign):

obfuscation
dependency-confusion
typosquatting
clones-real-package
infostealer

Malicious versions

4 flagged

0.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

697b56a6de305412973432c5b3408cf52f8a6aae0aedfbb64e2dad666c7b09b6

d91767b12efcd1ad71b86b8d6770f33ddd3f1bfdec795dc04fd1d743a63a4591

Detection & response playbook

Credential / info stealer

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

Campaign

2024-11-asn1tool

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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