Malicious Code Injection in nokire-akaza34: A Threat to npm Ecosystem
Summary
MAL-2025-162246: Malicious code in nokire-akaza34 (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-akaza34' 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 publishing scripts, which can lead to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in 'nokire-akaza34' 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, effectively polluting the npm registry. This can lead to unauthorized access and manipulation of projects that depend on this package, potentially compromising sensitive data and application integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza34If 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-akaza34' package and replace it with a trusted alternative. Always verify the source and integrity of packages before including them in your project.
Conclusion
The 'nokire-akaza34' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for nokire-akaza34 →
FAQ
The main risk is the potential for unauthorized modifications to your project's dependencies, which can lead to security breaches and data loss.
You can check your package.json and package-lock.json files for any references to 'nokire-akaza34' or use tools like Vulert to scan your project.
Immediately uninstall the package using 'npm uninstall nokire-akaza34' and review your project's dependencies for any other malicious packages.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities, ensuring your application remains secure.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.
