Malicious Code Injection in nokire-kore36: A Threat to npm Ecosystem
Summary
MAL-2025-162724: Malicious code in nokire-kore36 (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-kore36' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This specific package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-kore36' originates from its design to include malicious scripts that modify the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications that depend on this package, potentially allowing for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore36If 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 prevent the installation of this package by using the following command to uninstall it: npm uninstall nokire-kore36. Additionally, consider using a package-lock.json file to lock down your dependencies and avoid unintentional updates to vulnerable packages.
Conclusion
The 'nokire-kore36' package poses a significant threat due to its malicious code designed to manipulate package metadata and republish variants. Users are advised to uninstall this package and monitor their applications for any signs of compromise. Utilizing tools like Vulert can enhance security by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for nokire-kore36 →
FAQ
The main risk is that it can modify your project's package.json file, leading to the installation of malicious variants and potentially compromising your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
You should uninstall the package immediately and monitor your project for any unusual behavior.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities using just your package-lock.json file.
While npm packages are generally safe, it is crucial to regularly check for vulnerabilities and only use trusted packages to minimize risks.
