Which versions of asciidrawing are malicious?

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

How do I remediate asciidrawing if I installed it?

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

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

Yes — asciidrawing is associated with the RLMA-2024-07834, 2024-09-sampleuser123-asciidrawing 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 asciidrawing 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 asciidrawing (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asciidrawing across your stack and pipelines.

Malicious package

asciidrawingPyPI

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

MAL-2024-9944

Immediate action

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

pip uninstall asciidrawing

What this malware does

During installation, a Discord webhook is used to exfiltrate basic data. The package seems to attempt impersonating the "asciidraw" package (some files and description in setup.py are copied).

The other package, pdf2doc, as well as time correlation suggests the uploader is related to the 2024-09-bondonioanderas-cryptominer campaign as well.

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

Campaign: 2024-09-sampleuser123-asciidrawing

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
impersonation
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
clones-real-package
dependency-confusion

The OpenSSF Package Analysis project identified 'asciidrawing' @ 0.1.2 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.1.10.1.2

Indicators of compromise (SHA-256)

24cf3acf1b2bea67c15883ad235855bc9cb0687b5e61819c83ac73c5e0a6f3ac

2dd9ac0d2ef9e9bb84011c475ec24faabed0759dfceb9385fc5904e42f045029

d2a9162ee0759b5f5b7e19384bd2b1f13aa36214797e4a099d6960ea0da4f7a7

633d53a1b6bcde673f71f2788cc6c268f7eef20552eb7a0dc3f533f6a9a7ad12

4a33f450171fccce762c65b1ed1296012b4dbdf92c1507c5ad07957c43ca7d50

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 asciidrawing (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asciidrawing across your stack and pipelines.
If you installed it — respond
asciidrawing 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 asciidrawing 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 asciidrawing 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. asciidrawing on PyPI has been identified as a malicious package (versions 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-078342024-09-sampleuser123-asciidrawing

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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