Malicious Code Injection in nokire-kilua3: A Threat to npm Ecosystem
Summary
MAL-2025-162617: Malicious code in nokire-kilua3 (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-kilua3' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality through reusable code. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with random names, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-kilua3' stems from its involvement in the tea.xyz token reward campaign. This package contains scripts designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. This could lead to security risks for applications relying on these packages, as they may inadvertently use compromised versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kilua3If 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 'nokire-kilua3' and any packages that may depend on it. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-kilua3' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from potential threats.
See every vulnerability recorded for nokire-kilua3 →
FAQ
'nokire-kilua3' is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the use of compromised packages, which may introduce security risks and affect the integrity of your application.
You should uninstall 'nokire-kilua3' immediately using 'npm uninstall nokire-kilua3' and audit your dependencies for any other vulnerabilities.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies.
