Malicious Code Injection in nabuf-ogaf-doiko: A Threat to npm Ecosystem
Summary
MAL-2025-161310: Malicious code in nabuf-ogaf-doiko (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-doiko is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package is designed to automatically generate and publish derivative packages, making it a potential risk for developers who rely on npm for their projects.
Vulnerability Detail
The vulnerability in nabuf-ogaf-doiko arises from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The malicious payload is part of a broader scheme to exploit the npm ecosystem, leading to potential security risks for applications that depend on this package. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabuf-ogaf-doikoIf 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 file to monitor dependencies. Ensure that your project does not include nabuf-ogaf-doiko or any of its derivatives. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The nabuf-ogaf-doiko package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and publish unauthorized derivatives. It is crucial for developers to be vigilant and remove this package from their projects to maintain security and integrity.
See every vulnerability recorded for nabuf-ogaf-doiko →
FAQ
nabuf-ogaf-doiko is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and unstable dependencies into your project.
You should uninstall the package immediately using the command 'npm uninstall nabuf-ogaf-doiko' and check for any other affected dependencies.
You can use tools like Vulert to monitor your project's dependencies for vulnerabilities in real-time, helping you to stay informed about potential risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
