Which versions of asciitranslator are malicious?

The following npm versions of asciitranslator are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate asciitranslator if I installed it?

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

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

Yes — asciitranslator is associated with the GHSA-77fr-xww7-mp2f 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 asciitranslator 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 asciitranslator (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asciitranslator across your stack and pipelines.

Malicious package

asciitranslatornpm

Malicious code in asciitranslator (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191065

Immediate action

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

npm uninstall asciitranslator

What this malware does

The package asciitranslator was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

ec7fadae6b8c223ab9f503f09922adb5c92ed520a19dde2b624c85176f4ecd51

476d8e927f4bd1e2707ea0afb454ba78a4710bbc7aabeff125712c176bb3660f

327f54d9fbc5fbd8fbb3edc517dc19c9a8a43791a1f693db85d8e259d4c3dd37

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

Campaign

GHSA-77fr-xww7-mp2f

References

Credits

Amazon Inspector · finder

Detect & block this

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