Critical Malicious Code Vulnerability in tokenshower Package

tokenshower Updated 19 Mar 2026

Summary

19/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1926: Malicious code in tokenshower (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tokenshower package is a Node.js library available through npm, designed to facilitate token management in various applications. It is commonly used for handling authentication tokens securely. However, this package has been identified as containing malicious code, posing a significant risk to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the tokenshower package. This code can compromise the security of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there may still be residual effects on the system, as full control may have been granted to an external entity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tokenshower

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no effective workarounds for this vulnerability other than complete removal of the tokenshower package and securing your environment.

Conclusion

The tokenshower package has been identified as containing malicious code that poses a serious security risk. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for tokenshower →

Share this vulnerability

FAQ

You should uninstall the tokenshower package immediately and rotate any secrets or keys stored on the affected machine.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Leaving the tokenshower package installed can lead to unauthorized access to sensitive information and potential full control of your system by malicious actors.

The best recovery method is to uninstall the package and rotate any compromised secrets or keys. There is no guarantee that simply removing the package will eliminate all malicious effects.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tokenshower

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback