Malicious Code Detected in nokire-akaza81: npm Package Vulnerability
Summary
MAL-2025-162298: Malicious code in nokire-akaza81 (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 nokire-akaza81 package 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 for token rewards, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in nokire-akaza81 originates from its association with the tea.xyz token reward campaign. The package 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 pollutes the npm registry and can compromise the integrity of other packages within the ecosystem. The malicious payload can potentially affect any project that depends on this package, leading to security risks and loss of trust in the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza81If 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-akaza81 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before including them in your project.
Conclusion
The nokire-akaza81 package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package from their projects and to adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for nokire-akaza81 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores through automated publishing of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help identify if your application is affected by this vulnerability.
If you have installed nokire-akaza81, you should uninstall it immediately using the command npm uninstall nokire-akaza81 and look for alternative packages.
While specific alternatives depend on the functionality you need, it is advisable to search for reputable packages on npm that serve similar purposes without the associated risks.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure you only install packages from trusted sources.
