Malicious Code Injection in ita-43: A Threat to npm Packages
Summary
MAL-2025-156960: Malicious code in ita-43 (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-43' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, notorious for flooding the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'ita-43' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The malicious behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially affecting any project that depends on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ita-43If 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, avoid using the 'ita-43' package and consider using alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before including them in your project.
Conclusion
The 'ita-43' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and to adopt best practices for dependency management to avoid similar vulnerabilities in the future.
See every vulnerability recorded for ita-43 →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Immediately uninstall the package using 'npm uninstall ita-43' and review your project's dependencies for any other potentially malicious packages.
While specific exploits are not detailed, the vulnerability allows for the manipulation of package metadata, which can lead to further security issues in dependent projects.
Regularly audit your dependencies, use trusted sources for packages, and consider implementing tools like Vulert to monitor for vulnerabilities.
