Malicious Code Injection in nabuf-otgigaf-dajafi: A Threat to npm Ecosystem
Summary
MAL-2025-161401: Malicious code in nabuf-otgigaf-dajafi (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 nabuf-otgigaf-dajafi is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in nabuf-otgigaf-dajafi originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only affects the affected package but also contributes to the overall degradation of the npm registry by continuously republishing variants, making it difficult for developers to find legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabuf-otgigaf-dajafiIf 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 nabuf-otgigaf-dajafi package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes that may indicate the presence of malicious packages.
Conclusion
The nabuf-otgigaf-dajafi package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for nabuf-otgigaf-dajafi →
FAQ
nabuf-otgigaf-dajafi is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially compromising your project's security.
You should remove the nabuf-otgigaf-dajafi package from your project immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
