Malicious Code Injection in nokire-akaza83: A Threat to npm Ecosystem
Summary
MAL-2025-162300: Malicious code in nokire-akaza83 (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-akaza83 is part of a series of malicious packages associated with the tea.xyz token reward campaign that has infiltrated the npm ecosystem. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, posing a significant risk to the integrity of the npm registry and developers relying on it.
Vulnerability Detail
The vulnerability in nokire-akaza83 stems from its malicious payload, which 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, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The origin of this vulnerability is linked to the broader campaign aimed at exploiting the npm ecosystem for token rewards, making it a significant concern for developers and users of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza83If 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 affected package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The vulnerability in nokire-akaza83 highlights the risks associated with malicious packages in the npm ecosystem. Developers must remain vigilant by regularly updating their dependencies and utilizing tools like Vulert to monitor for vulnerabilities. Removing affected packages and replacing them with trusted alternatives is crucial to maintaining the security and integrity of your projects.
See every vulnerability recorded for nokire-akaza83 →
FAQ
Nokire-akaza83 is a malicious npm package that is part of a campaign to exploit the npm ecosystem for token rewards.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability to your project.
You should uninstall the package immediately using the command npm uninstall nokire-akaza83 and check for any other malicious packages.
Regularly update your dependencies, monitor your package-lock.json with tools like Vulert, and be cautious of packages with low usage or unknown origins.
Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can check if your application is affected by vulnerabilities using the Vulert playground without any signup.
