Malicious Code Vulnerability in nokire-akaza2: Exploitation of npm Packages
Summary
MAL-2025-162231: Malicious code in nokire-akaza2 (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-akaza2' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.
Vulnerability Detail
The vulnerability in 'nokire-akaza2' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the broader tea.xyz token reward campaign, which has been identified as a source of malicious packages flooding the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza2If 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-akaza2' package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The 'nokire-akaza2' package presents a significant security risk due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their applications.
See every vulnerability recorded for nokire-akaza2 →
FAQ
The primary risk is that it modifies your package.json file and floods the npm registry with malicious variants, potentially compromising your project's integrity.
You can use Vulert to analyze your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected.
You should immediately remove the package from your project and monitor for any updates or patches that may be released.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities without requiring code access or installation.
Look for alternative packages that offer similar functionality but do not have known vulnerabilities. Always prioritize security when selecting dependencies.
