Critical Malicious Code Vulnerability in Internationalized Package
Summary
MAL-2026-743: Malicious code in internationalized (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 'internationalized' package is a Node.js library designed to facilitate the handling of internationalization in applications. It allows developers to manage translations and locale-specific formats effectively. However, this package has been compromised, leading to severe security risks for any application utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of malicious code embedded within the 'internationalized' package. This code can fully compromise any computer that has the package installed, allowing attackers to access sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be harmful and can lead to unauthorized control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall internationalizedIf 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, you can isolate the affected system from the network to prevent further exploitation while you work on removing the package and securing your environment.
Conclusion
The 'internationalized' package has been compromised with malicious code, posing significant risks to any system using it. Immediate action is required to remove the package and secure sensitive information. Utilize tools like Vulert for ongoing monitoring of your dependencies to prevent future vulnerabilities.
See every vulnerability recorded for internationalized →
FAQ
You should remove the package immediately and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is impacted by this vulnerability without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.
Yes, Vulert can monitor your package-lock.json file to alert you in real-time for any open-source vulnerabilities in your software.
Given the nature of the compromise, it is advisable to avoid using the 'internationalized' package until a verified and secure version is released.
