Malicious Code Injection in nokire-akaza55: A Threat to npm Ecosystem
Summary
MAL-2025-162269: Malicious code in nokire-akaza55 (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-akaza55' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-akaza55' stems from its inclusion in a campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages available to developers, potentially leading to security risks and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza55If 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-akaza55' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package management practices, such as using a private npm registry or employing tools to audit your dependencies for known vulnerabilities.
Conclusion
The 'nokire-akaza55' package poses a significant threat to the npm ecosystem due to its malicious behavior of flooding the registry with derivative packages. It is crucial for developers to take immediate action to remove this package and implement best practices for dependency management to safeguard their projects.
See every vulnerability recorded for nokire-akaza55 →
FAQ
'nokire-akaza55' is an npm package identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall nokire-akaza55' and check your package-lock.json for any references to it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the packages you include in your projects.
