Malicious Code Injection in nokire-akaza47: A Threat to npm Ecosystem
Summary
MAL-2025-162260: Malicious code in nokire-akaza47 (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-akaza47' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these packages in their projects.
Vulnerability Detail
The vulnerability in 'nokire-akaza47' originates from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to security risks for developers who may inadvertently install these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza47If 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, avoid using the 'nokire-akaza47' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-akaza47' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain a secure development environment.
See every vulnerability recorded for nokire-akaza47 →
FAQ
The main risk is the potential for malicious code execution, which can compromise your application and expose sensitive data.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately and review your project's dependencies for any other potentially malicious packages.
Yes, Vulert provides a service that monitors your package-lock.json for vulnerabilities in real-time.
Regularly audit your dependencies, use trusted packages, and keep your packages updated to the latest versions.
