Malicious Code Injection in nokire-kore32: A Threat to npm Users
Summary
MAL-2025-162720: Malicious code in nokire-kore32 (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-kore32' is part of a series of malicious packages that emerged during 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. This behavior not only clutters the npm registry but also poses significant security risks to users who may unknowingly install these compromised packages.
Vulnerability Detail
The vulnerability in 'nokire-kore32' originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This malicious payload allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised software by unsuspecting developers. The ramifications include exposure to further vulnerabilities and the risk of executing malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore32If 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 'nokire-kore32' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.
Conclusion
The 'nokire-kore32' package poses a significant security risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for nokire-kore32 →
FAQ
'nokire-kore32' is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
You can check if your project is affected by using tools like Vulert, which monitors your package-lock.json for vulnerabilities without requiring code access.
If you have installed 'nokire-kore32', you should uninstall it immediately using 'npm uninstall nokire-kore32' and check for any other suspicious packages.
Yes, Vulert provides a service that monitors open-source vulnerabilities in your software by analyzing your package-lock.json file.
Regularly check for updates to your packages and subscribe to security advisories related to the npm ecosystem.
