Malicious Code Injection in nokire-rara11: A Threat to npm Ecosystem
Summary
MAL-2025-163297: Malicious code in nokire-rara11 (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-rara11' is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with altered names and metadata. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.
Vulnerability Detail
The vulnerability in 'nokire-rara11' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, effectively polluting the npm registry and inflating developer reputation scores for token rewards. The origin of this issue is linked to automated scripts that are part of the package, which are designed to exploit the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-rara11If 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 'nokire-rara11' and any other suspicious packages that may be part of the tea.xyz token reward campaign. Regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-rara11' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove such packages can help safeguard your projects.
See every vulnerability recorded for nokire-rara11 →
FAQ
'nokire-rara11' is a malicious npm package that is part of a campaign to exploit the npm registry by publishing derivative packages with altered metadata.
Using 'nokire-rara11' can compromise your project's integrity, lead to the use of tainted packages, and potentially expose you to security risks.
You should immediately uninstall 'nokire-rara11' using 'npm uninstall nokire-rara11' and audit your project for any other malicious packages.
You can use tools like 'npm audit' to check for vulnerabilities in your dependencies. Additionally, you can use Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
