Malicious Code Injection in additional_kite_requirement Package
Summary
MAL-2025-93127: Malicious code in additional_kite_requirement (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 additional_kite_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. The malicious behavior of this package poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the additional_kite_requirement package, which contains scripts that automatically modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem, as it complicates the identification of legitimate packages and can potentially introduce harmful code into projects that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall additional_kite_requirementIf 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 additional_kite_requirement package and any packages that depend on it. Monitor your project's dependencies closely and consider using tools like Vulert to scan for vulnerabilities in your package-lock.json file.
Conclusion
The additional_kite_requirement package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is essential for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying vigilant and informed is key to maintaining the security of your software.
See every vulnerability recorded for additional_kite_requirement →
FAQ
It is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.
This vulnerability can compromise the integrity of your project by introducing malicious code and making it difficult to identify legitimate packages.
You should uninstall the additional_kite_requirement package immediately and review your project dependencies for any related vulnerabilities.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
