Which versions of token-discord-encryptation are malicious?

Every published version of token-discord-encryptation on npm is considered malicious. Remove the package entirely.

How do I remediate token-discord-encryptation if I installed it?

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

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

Yes — token-discord-encryptation is associated with the GHSA-q5w4-82wp-c3hp 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 token-discord-encryptation 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 token-discord-encryptation (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-discord-encryptation across your stack and pipelines.

Malicious package

token-discord-encryptationnpm

Malicious code in token-discord-encryptation (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1157

Immediate action

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

npm uninstall token-discord-encryptation

What this malware does

The package token-discord-encryptation 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

4eb2acc0d57e1e82a392c8ea8d8531c42547516e312acef7f16e72175ddccd05

38c8f046fd4903192eb3de371ca4df10734635758b721d7cf2827f9df6f84f0d

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

Campaign

GHSA-q5w4-82wp-c3hp

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks token-discord-encryptation-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