Malicious Code Injection in sabudaaopa-muyafafig-bafua Package

sabudaaopa-muyafafig-bafua Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165516: Malicious code in sabudaaopa-muyafafig-bafua (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sabudaaopa-muyafafig-bafua package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the sabudaaopa-muyafafig-bafua package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and damage to the reputation of the npm ecosystem.

How To Fix

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

npm uninstall sabudaaopa-muyafafig-bafua

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 workaround, you can monitor your project for any unintended installations of this package and ensure that your package-lock.json file is kept secure. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your dependencies.

Conclusion

The sabudaaopa-muyafafig-bafua package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. Immediate action is required to remove the package and prevent further issues. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for sabudaaopa-muyafafig-bafua →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately using 'npm uninstall sabudaaopa-muyafafig-bafua' and monitor your project for any further issues.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid installing packages from untrusted sources.

Yes, Vulert can monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

How To Fix

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

npm uninstall sabudaaopa-muyafafig-bafua

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