Malicious Code Injection in nokire-kore1 Package: A Threat to npm Users
Summary
MAL-2025-162695: Malicious code in nokire-kore1 (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 nokire-kore1 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been implicated in a malicious campaign that aims to exploit the npm registry. It is designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for their projects.
Vulnerability Detail
The vulnerability in the nokire-kore1 package stems from its involvement in the tea.xyz token reward campaign. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The malicious payload can potentially allow unauthorized access to sensitive data or lead to the installation of further malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore1If 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 nokire-kore1 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The nokire-kore1 package poses a significant security threat due to its malicious code designed to exploit the npm registry. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for nokire-kore1 →
FAQ
The nokire-kore1 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the nokire-kore1 package immediately and check for any other affected packages in your project.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
