Malicious Code Injection in nokire-rara69: A Threat to npm Ecosystem
Summary
MAL-2025-163360: Malicious code in nokire-rara69 (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-rara69' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-rara69' originates from its malicious code that modifies 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 action pollutes the npm registry and can potentially compromise other packages and applications relying on npm for dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-rara69If 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 avoid using the 'nokire-rara69' package and any other packages that may be part of the tea.xyz campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The 'nokire-rara69' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package and utilize tools like Vulert to monitor for vulnerabilities in your projects.
See every vulnerability recorded for nokire-rara69 →
FAQ
The primary risk is that it modifies your package.json file, potentially leading to the exposure of sensitive information and the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify affected packages.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing packages from untrusted sources.
Immediately uninstall the package using 'npm uninstall nokire-rara69' and review your project for any other suspicious packages.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
