Malicious Code Injection in nokire-kilua35: A Threat to npm Users
Summary
MAL-2025-162623: Malicious code in nokire-kilua35 (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 'nokire-kilua35' 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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-kilua35' originates from its involvement in a malicious campaign 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 variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload can potentially allow unauthorized access to sensitive data or lead to the installation of further malicious dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kilua35If 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 manually remove the 'nokire-kilua35' package from your project by executing the command: 'npm uninstall nokire-kilua35'. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
Conclusion
The 'nokire-kilua35' package poses a significant threat to npm users due to its malicious behavior. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for nokire-kilua35 →
FAQ
'nokire-kilua35' is an npm package that has been identified as malicious due to its involvement in a token reward campaign that manipulates package metadata.
The vulnerability can lead to unauthorized modifications of your package dependencies, potentially introducing further security risks and compromising your application's integrity.
You should uninstall the package immediately and monitor your project for any unusual behavior. Consider using tools like Vulert to check for other vulnerabilities.
Yes, regularly audit your dependencies using tools like npm audit and monitor your package-lock.json with Vulert to catch vulnerabilities early.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
