Malicious Code Injection in nokire-akaza6: A Threat to npm Ecosystem
Summary
MAL-2025-162274: Malicious code in nokire-akaza6 (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-akaza6' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with random names. This behavior is intended to inflate developer reputation scores in exchange for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-akaza6' originates from its malicious code that modifies the package.json file to remove private flags and alters 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 projects that inadvertently depend on these malicious packages, leading to potential exploitation and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza6If 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 'nokire-akaza6' and any other packages that are part of the tea.xyz campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The 'nokire-akaza6' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publication and inflate developer reputations. It is essential to remove this package and regularly audit your dependencies to maintain the security of your projects.
See every vulnerability recorded for nokire-akaza6 →
FAQ
'nokire-akaza6' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially leading to exploitation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, Vulert can help you identify affected packages.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
Remove any identified malicious packages immediately and replace them with secure alternatives. Ensure to audit your project regularly.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
