Malicious Code Injection in nokire-kore42: A Threat to npm Ecosystem
Summary
MAL-2025-162731: Malicious code in nokire-kore42 (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-kore42' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-kore42' originates from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore42If 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 'nokire-kore42' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The 'nokire-kore42' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying and republishing packages. It is crucial for developers to regularly audit their dependencies and remove any malicious packages to maintain the integrity and security of their applications.
See every vulnerability recorded for nokire-kore42 →
FAQ
The primary risk is that it modifies critical files and republish variants, which can lead to security vulnerabilities in applications that depend on it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-kore42' and check your package-lock.json for any remnants.
Yes, tools like npm audit and Vulert can help identify and alert you to malicious packages in your dependencies.
Using compromised packages can lead to data breaches, unauthorized access, and overall instability in your application, making it crucial to maintain secure dependencies.
