Malicious Code Injection in nabuf-oof-doto Package - npm Vulnerability
Summary
MAL-2025-161380: Malicious code in nabuf-oof-doto (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 nabuf-oof-doto package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.
Vulnerability Detail
The vulnerability in the nabuf-oof-doto package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabuf-oof-dotoIf 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package. Regularly audit your dependencies and consider using tools like Vulert to monitor for vulnerabilities in your open-source packages.
Conclusion
The nabuf-oof-doto package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for nabuf-oof-doto →
FAQ
The nabuf-oof-doto package is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.
You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring any signup.
If you have installed nabuf-oof-doto, you should uninstall it immediately using 'npm uninstall nabuf-oof-doto' and check your package-lock.json for any references to it.
Yes, Vulert provides a service that monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.
Using malicious packages can lead to security vulnerabilities, data breaches, and the potential for your application to be compromised or misused.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
