Critical Security Breach in @productdevbook/auth: Malicious Code Injection
Summary
MAL-2025-191302: Malicious code in @productdevbook/auth (npm). Affects @productdevbook/auth versions 0.2.2. 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 @productdevbook/auth package is an npm library designed for authentication processes in web applications. It provides essential functionalities for managing user authentication, including token generation and credential verification. However, this package has been compromised, making it vulnerable to severe security threats that can affect users and their applications.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @productdevbook/auth package. This malicious code is designed to steal user tokens and credentials, subsequently publishing them to GitHub. The worm can propagate to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying the user's home directory, leading to potential data loss and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @productdevbook/authIf 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 temporary workaround, users are advised to remove the @productdevbook/auth package from their project until a secure version is available. This can be done using the command: npm uninstall @productdevbook/auth. Additionally, consider using alternative authentication libraries that are not affected by this vulnerability.
Conclusion
The @productdevbook/auth package has been compromised by a malicious worm that poses significant security risks. Users must take immediate action to update their packages and consider alternative solutions to safeguard their applications. Regular monitoring and vulnerability assessments are essential to maintain security.
See every vulnerability recorded for @productdevbook/auth →
FAQ
The vulnerability involves malicious code that steals user tokens and credentials, potentially leading to unauthorized access and data breaches.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you suspect that your application has been compromised, immediately revoke any stolen tokens and credentials, and update your packages to secure versions.
Yes, a patched version of the @productdevbook/auth package is available. Users should update to the latest version to mitigate the risk.
Failure to address this vulnerability can lead to unauthorized access to user accounts, data loss, and potential damage to your application's reputation.
