Critical Malicious Code Vulnerability in passport-google-auth-token Package
Summary
MAL-2026-230: Malicious code in passport-google-auth-token (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The passport-google-auth-token package is a Node.js library that facilitates authentication with Google using OAuth tokens. It is commonly used in web applications to streamline user login processes. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the passport-google-auth-token package. This code can fully compromise 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 simply removing the package may not eliminate all traces of the compromise, as full control of the affected system 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 passport-google-auth-tokenIf 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, if you need to maintain Google authentication functionality, consider using alternative packages that provide similar capabilities without the associated risks. Always ensure to review the security history of any package before installation.
Conclusion
The discovery of malicious code in the passport-google-auth-token package highlights the importance of vigilance when using open-source libraries. Developers should take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help in proactively monitoring for vulnerabilities in the future.
See every vulnerability recorded for passport-google-auth-token →
FAQ
Immediately uninstall the package using 'npm uninstall passport-google-auth-token' and rotate any sensitive information stored on the affected system.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Keeping the package installed poses a significant security risk, as it can lead to unauthorized access to sensitive data and full control of your system by malicious actors.
Yes, consider using other authentication libraries that do not have a history of malicious code, such as 'passport-google-oauth20' or 'google-auth-library'.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your applications remain secure.
