Malicious Code Injection in nokiragne-aai: A Threat to npm Ecosystem
Summary
MAL-2025-162078: Malicious code in nokiragne-aai (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 'nokiragne-aai' 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 scripts that publish numerous variants of the original package, potentially compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokiragne-aai' originates from its association with 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 leads to the continuous republishing of these variants, which can pollute the npm registry and mislead developers into using compromised packages. The ramifications include potential security risks for applications relying on these packages, as they may inadvertently incorporate malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokiragne-aaiIf 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 'nokiragne-aai' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'nokiragne-aai' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for nokiragne-aai →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed nokiragne-aai, it is recommended to uninstall the package and check for any updates or alternatives.
While specific exploits have not been detailed, the potential for malicious code execution exists due to the nature of the vulnerability.
This vulnerability can lead to a polluted npm registry, making it difficult for developers to find trustworthy packages and increasing the risk of incorporating malicious code.
