Malicious Code Injection in ninakusuma: A Threat to npm Packages
Summary
MAL-2025-171658: Malicious code in ninakusuma (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
Ninakusuma is an npm package that has been identified as part of a larger scheme involving the tea.xyz token reward campaign. This campaign has led to the proliferation of numerous npm packages that are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages. The ninakusuma package, like others in this campaign, contains scripts that can alter its own metadata and republish itself under various names, potentially leading to a polluted npm registry.
Vulnerability Detail
The vulnerability in the ninakusuma package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the package itself but also poses a risk to the broader npm ecosystem by flooding it with potentially harmful packages. The malicious payload is designed to continuously republish variants, which can confuse developers and lead to unintentional usage of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ninakusumaIf 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 ninakusuma package and any other packages associated with the tea.xyz campaign. If you have already installed it, you can remove it using the command: npm uninstall ninakusuma.
Conclusion
The ninakusuma package poses a significant risk due to its malicious behavior linked to the tea.xyz token reward campaign. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects by removing affected packages and utilizing monitoring tools like Vulert.
See every vulnerability recorded for ninakusuma →
FAQ
Ninakusuma is an npm package that has been linked to a malicious campaign aimed at manipulating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the ninakusuma package immediately using the command: npm uninstall ninakusuma.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for security advisories, and utilize tools like Vulert to keep track of vulnerabilities in your packages.
