Malicious Code Injection in nabuf-ogaf-doiofo: A Threat to npm Packages
Summary
MAL-2025-161312: Malicious code in nabuf-ogaf-doiofo (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
Background
The package nabuf-ogaf-doiofo is part of a broader campaign targeting npm packages, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system, creating numerous derivative packages to inflate developer reputation scores. It is crucial for developers to understand the risks associated with such packages, as they can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in nabuf-ogaf-doiofo stems 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 to clutter the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation by attackers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabuf-ogaf-doiofoIf 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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include nabuf-ogaf-doiofo in its dependencies. You can also utilize tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The nabuf-ogaf-doiofo package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers must take proactive steps to remove such packages and utilize tools like Vulert to monitor their projects for vulnerabilities. Understanding and addressing these risks is crucial for maintaining the security of software applications.
See every vulnerability recorded for nabuf-ogaf-doiofo →
FAQ
nabuf-ogaf-doiofo is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can lead to dependency confusion, where your project may inadvertently use malicious packages, compromising security and integrity.
Immediately uninstall the package using npm uninstall nabuf-ogaf-doiofo and review your project's dependencies for any other potentially malicious packages.
Yes, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure you only install packages from trusted sources.
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 needing to sign up.
