Malicious Code Injection in ita-35: A Threat to npm Ecosystem
Summary
MAL-2025-156951: Malicious code in ita-35 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'ita-35' 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 known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior raises significant concerns regarding the integrity and security of the npm registry.
Vulnerability Detail
The vulnerability in 'ita-35' originates from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The malicious scripts included in this package are designed to automate the process of creating and publishing these harmful derivatives, which can lead to a loss of trust in the npm ecosystem and expose developers to security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ita-35If 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 avoid using the 'ita-35' package and any packages that depend on it. Monitor your package-lock.json file for any unauthorized changes and revert them if necessary.
Conclusion
The 'ita-35' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Removing the package and ensuring the security of your project is imperative to maintaining a safe development environment.
See every vulnerability recorded for ita-35 →
FAQ
The ita-35 vulnerability can lead to the pollution of the npm registry, compromising the integrity of other packages and potentially exposing developers to security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can check if your application is affected without any signup.
If you have installed ita-35, you should uninstall it immediately using the command 'npm uninstall ita-35' and review your other dependencies for any potential vulnerabilities.
No patches are available for ita-35 as it is a malicious package. The best course of action is to remove it from your project.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
