Malicious Code Injection in nokire-akaza1: A Threat to npm Ecosystem
Summary
MAL-2025-162219: Malicious code in nokire-akaza1 (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-akaza1 is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated scripts that publish numerous derivative packages with randomized names.
Vulnerability Detail
The vulnerability in nokire-akaza1 originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a significant risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation of their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza1If 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-akaza1 package altogether. If it is already part of your project, consider removing it by executing: npm uninstall nokire-akaza1. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for any open-source vulnerabilities.
Conclusion
The nokire-akaza1 package poses a significant risk due to its malicious code designed to manipulate npm's package registry. It is essential for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential exploitation.
See every vulnerability recorded for nokire-akaza1 →
FAQ
Nokire-akaza1 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed nokire-akaza1, you should uninstall it immediately and check for any other potentially compromised packages in your project.
Yes, tools like Vulert can monitor your package-lock.json file in real-time for open-source vulnerabilities, helping you stay informed about potential threats.
