Malicious Code Injection in nokire-akaza37: A Threat to npm Packages
Summary
MAL-2025-162249: Malicious code in nokire-akaza37 (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-akaza37' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of such packages is to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-akaza37' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, thereby polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in the package (such as auto.js and autopublish.js) automate these harmful actions, posing a risk to developers who may unknowingly use or depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-akaza37If 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 workaround, you can manually check your package-lock.json file for any references to 'nokire-akaza37' and remove it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.
Conclusion
The 'nokire-akaza37' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in the future.
See every vulnerability recorded for nokire-akaza37 →
FAQ
'nokire-akaza37' is an npm package that has been identified as malicious, associated with a token reward campaign that manipulates package metadata.
The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and compromising the integrity of your project.
You should remove the package immediately and check your project for any dependencies that may have been affected.
Yes, regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application using just your package-lock.json file.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
