Malicious Code Injection in nabuf-otin-agog: npm Package Vulnerability
Summary
MAL-2025-161500: Malicious code in nabuf-otin-agog (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 'nabuf-otin-agog' package 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 aimed at inflating developer reputation scores through the tea.xyz token reward system. The package is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the software supply chain.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the 'nabuf-otin-agog' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to a cluttered npm registry and potential security risks for developers who unknowingly depend on these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing capabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nabuf-otin-agogIf 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, avoid using the 'nabuf-otin-agog' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities.
Conclusion
The 'nabuf-otin-agog' package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their software.
See every vulnerability recorded for nabuf-otin-agog →
FAQ
The 'nabuf-otin-agog' package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the tea.xyz token reward system.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages. It may also expose your project to security risks if you inadvertently depend on compromised packages.
Remove the 'nabuf-otin-agog' package from your project and monitor for any updates or patches. Use tools like Vulert to check for vulnerabilities in your package-lock.json file.
Yes, you can use Vulert, which requires only your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
