Malicious Code Vulnerability in nokire-kore34: Exploitation of npm Registry
Summary
MAL-2025-162722: Malicious code in nokire-kore34 (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-kore34' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign, which aimed to manipulate npm's ecosystem. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly incorporate these packages into their projects.
Vulnerability Detail
The vulnerability in 'nokire-kore34' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This manipulation allows the package to continuously republish variants, thereby polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who may inadvertently use these compromised packages, leading to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore34If 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, avoid using the 'nokire-kore34' package and monitor your dependencies for any signs of similar malicious packages. Regularly audit your package-lock.json file to identify and remove any potentially harmful packages.
Conclusion
The 'nokire-kore34' package represents a significant threat within the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their projects against such malicious exploits.
See every vulnerability recorded for nokire-kore34 →
FAQ
'nokire-kore34' is a malicious npm package that is part of a campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Using 'nokire-kore34' can lead to security vulnerabilities, including data breaches and exploitation of your application due to the malicious code embedded within.
It is recommended to audit your npm packages regularly, ideally after every major update or addition of new packages, to ensure no malicious packages are included.
If you discover a malicious package, immediately remove it from your project and report it to the npm registry to prevent others from being affected.
