Which versions of showdownxss are malicious?

Every published version of showdownxss on npm is considered malicious. Remove the package entirely.

How do I remediate showdownxss if I installed it?

Remove showdownxss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed showdownxss — how do I know if it already compromised me?

If showdownxss 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.

How do I find showdownxss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for showdownxss (all published versions).

Malicious package

showdownxssnpm

Advisory published Jan 2, 2026Updated Jan 2, 2026

showdownxss is a confirmed malicious npm package (MAL-2026-23) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in showdownxss (npm)

MAL-2026-23

Immediate action

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

npm uninstall showdownxss

What this malware does

The package showdownxss was found to contain malicious code.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

2bc880126bd2e6f146d20b5f0ffac063167334b69f8a27a8e39446e2aa60ab1a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for showdownxss (all published versions).
If you installed it — respond
Remove showdownxss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If showdownxss 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. showdownxss 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.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks showdownxss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database