Malicious Code Injection in nokire-akaza33: A Threat to npm Ecosystem
Summary
MAL-2025-162245: Malicious code in nokire-akaza33 (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-akaza33' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores. Such behavior not only undermines the integrity of the npm ecosystem but also poses significant risks to developers and users relying on these packages.
Vulnerability Detail
The vulnerability in 'nokire-akaza33' stems from its malicious code, which 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 to pollute the npm registry. This behavior can lead to a compromised development environment, where developers may unknowingly use malicious packages, potentially exposing their applications to further vulnerabilities or malicious attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza33If 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-akaza33' package and monitor your project's dependencies for any similar malicious packages. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file, ensuring your application remains secure.
Conclusion
The 'nokire-akaza33' package presents a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about their dependencies, regularly update their packages, and utilize tools like Vulert to ensure their applications remain secure from such vulnerabilities.
See every vulnerability recorded for nokire-akaza33 →
FAQ
'nokire-akaza33' is an npm package linked to a malicious campaign that aims to manipulate the npm registry by publishing numerous derivative packages.
Using 'nokire-akaza33' can compromise your project's integrity by introducing malicious code, which may lead to security breaches or data leaks.
You should uninstall 'nokire-akaza33' immediately using the command 'npm uninstall nokire-akaza33' and check your project for any other malicious dependencies.
Regularly update your packages, monitor your dependencies, and utilize tools like Vulert to scan for vulnerabilities in your package-lock.json.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without any installation.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
