Malicious Code Injection in nokire-akaza78: A Threat to npm Ecosystem
Summary
MAL-2025-162294: Malicious code in nokire-akaza78 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-akaza78' is part of a larger 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. Such behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'nokire-akaza78' originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This not only pollutes the npm registry but also compromises the security of applications that may inadvertently depend on these malicious packages. The ramifications include potential exposure to further vulnerabilities and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza78If 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-akaza78' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.
Conclusion
The 'nokire-akaza78' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry with derivative packages. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to maintain the security of their applications.
See every vulnerability recorded for nokire-akaza78 →
FAQ
The main issue is that it contains malicious code designed to manipulate the npm registry by publishing numerous derivative packages, which can compromise the integrity of your project.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can help identify if your application is at risk.
You should immediately uninstall the 'nokire-akaza78' package using 'npm uninstall nokire-akaza78' and audit your project for other potential vulnerabilities.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, ensuring your application remains secure.
Using malicious packages can lead to compromised security, data breaches, and a polluted development environment, making it crucial to regularly audit and manage dependencies.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
