Critical Malicious Code Vulnerability in token-verify-passport Package

token-verify-passport Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190633: Malicious code in token-verify-passport (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The token-verify-passport package is an npm library designed to facilitate the verification of tokens in web applications. It is commonly used for authentication purposes, allowing developers to ensure that tokens are valid and have not been tampered with. However, this package has been identified as containing malicious code, posing significant security risks to any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the token-verify-passport package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged as malware by security researchers, indicating that it may have been intentionally designed to exploit users' systems.

How To Fix

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

npm uninstall token-verify-passport

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

As a workaround, you can replace the functionality provided by token-verify-passport with an alternative package that offers similar features without the associated risks. Consider using well-maintained and reputable libraries for token verification, such as jsonwebtoken or passport-jwt.

Conclusion

The token-verify-passport package has been identified as containing malicious code that poses serious security risks. Immediate action is required to remove the package and secure any compromised secrets or keys. Utilizing alternative libraries and monitoring tools like Vulert can help prevent similar vulnerabilities in the future.

See every vulnerability recorded for token-verify-passport →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys that may have been compromised.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Using compromised packages can lead to unauthorized access to sensitive data, data breaches, and complete system compromise.

Yes, consider using libraries like jsonwebtoken or passport-jwt for token verification, which are well-maintained and have a good security track record.

How To Fix

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

npm uninstall token-verify-passport

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