Malicious Code Injection in ita-39: A Threat to npm Ecosystem
Summary
MAL-2025-156955: Malicious code in ita-39 (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 package 'ita-39' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with altered names and contents.
Vulnerability Detail
The vulnerability in 'ita-39' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload is designed to exploit the npm publishing mechanism, making it a significant threat to developers relying on npm for package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ita-39If 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, you can avoid using the 'ita-39' package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'ita-39' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can provide real-time alerts for any open-source vulnerabilities in your software.
See every vulnerability recorded for ita-39 →
FAQ
The vulnerability involves malicious code that alters package.json files and repackages them, leading to potential abuse of the npm registry.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.
You should remove 'ita-39' from your project and check for any alternative packages that do not pose a security risk.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.
Using 'ita-39' can lead to compromised package integrity, reputation inflation, and potential security risks for your application.
