Malicious Code Injection in nokire-kore29: A Threat to npm Packages
Summary
MAL-2025-162716: Malicious code in nokire-kore29 (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-kore29' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for developers and users relying on these packages.
Vulnerability Detail
The vulnerability in 'nokire-kore29' originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses risks of unintentional use of compromised packages by developers, leading to potential data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-kore29If 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-kore29' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The 'nokire-kore29' package poses a significant security risk due to its malicious code that alters project files and inflates developer reputation scores. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software projects.
See every vulnerability recorded for nokire-kore29 →
FAQ
The primary risk is that it can modify your project's package.json file and introduce malicious code, leading to potential security breaches.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall the package immediately using 'npm uninstall nokire-kore29' and monitor your project for any unusual behavior.
Yes, you should look for reputable packages that provide similar functionality but do not have a history of malicious behavior.
Regularly audit your dependencies using tools like Vulert and stay updated on security advisories for the packages you use.
