Malicious Code Injection in nabuf-otin-affgoa Package

nabuf-otin-affgoa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161490: Malicious code in nabuf-otin-affgoa (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The nabuf-otin-affgoa package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can lead to reputation inflation for developers participating in the tea protocol. Its functionality is compromised by malicious scripts that modify package metadata.

Vulnerability Detail

The vulnerability in nabuf-otin-affgoa stems from its inclusion in a malicious campaign that deploys scripts (such as auto.js and autopublish.js) to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nabuf-otin-affgoa

If 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-otin-affgoa package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to ensure no malicious packages are included.

Conclusion

The nabuf-otin-affgoa package poses significant risks due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package and monitor your project for similar vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for nabuf-otin-affgoa →

Share this vulnerability

FAQ

The nabuf-otin-affgoa package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you determine if your application is affected by this vulnerability.

Using compromised packages can lead to security vulnerabilities, data breaches, and the potential for your application to be exploited by malicious actors. It can also damage your project's reputation.

To prevent vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

If you have already used the nabuf-otin-affgoa package, uninstall it immediately and review your project for any dependencies that may have been affected. Consider using Vulert to check for other vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nabuf-otin-affgoa

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback