Malicious Code Injection in sabua-muyafig-buda Package

sabua-muyafig-buda Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165422: Malicious code in sabua-muyafig-buda (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 sabua-muyafig-buda package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically include scripts that automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the campaign.

Vulnerability Detail

The vulnerability in the sabua-muyafig-buda package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall sabua-muyafig-buda

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, consider removing the sabua-muyafig-buda package from your project and replacing it with a trusted alternative. You can do this by running: npm uninstall sabua-muyafig-buda.

Conclusion

The sabua-muyafig-buda package contains malicious code that poses a significant risk to applications relying on it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats.

See every vulnerability recorded for sabua-muyafig-buda →

Share this vulnerability

FAQ

The sabua-muyafig-buda package is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm registry.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and compromising your application's integrity.

If you have installed the sabua-muyafig-buda package, it is recommended to uninstall it immediately and check for any updates or patches.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you use for any known issues.

How To Fix

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

npm uninstall sabua-muyafig-buda

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