Critical Security Breach in @productdevbook/ts-i18n: Malicious Code Injection
Summary
MAL-2025-191305: Malicious code in @productdevbook/ts-i18n (npm). Affects @productdevbook/ts-i18n versions 1.4.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 package @productdevbook/ts-i18n is an npm library designed for internationalization in TypeScript applications. It facilitates the translation of applications into multiple languages, making it easier for developers to create globally accessible software. However, this package has been compromised, exposing users to severe security risks.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. It can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, there is a risk that the worm may destroy the user's home directory, leading to significant data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @productdevbook/ts-i18nIf 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 measure, users can remove the compromised package from their project by executing the following command: npm uninstall @productdevbook/ts-i18n. This will prevent the malicious code from executing while waiting for a patch.
Conclusion
The @productdevbook/ts-i18n package has been compromised by a malicious worm that poses serious security risks to users. Immediate action is required to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities in your software.
See every vulnerability recorded for @productdevbook/ts-i18n →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials and can also propagate to other npm packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall @productdevbook/ts-i18n' and monitor for any updates or patches.
Yes, the worm may destroy the user's home directory, leading to potential data loss.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.
