Malicious Code Injection in mutr-sds-bata: A Threat to npm Packages

mutr-sds-bata Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-161157: Malicious code in mutr-sds-bata (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

mutr-sds-bata is an npm package that appears to be part of a larger campaign aimed at exploiting the npm ecosystem. It is designed to facilitate the tea.xyz token reward system, which has been linked to the proliferation of malicious packages. The package's functionality is compromised by the presence of scripts that manipulate its metadata and behavior, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in mutr-sds-bata stems from its association with a malicious campaign that employs scripts to alter the package.json file. These scripts remove private flags, change version numbers, and generate random package names, effectively polluting the npm registry. This not only compromises the integrity of the package but also poses a risk to developers who may unknowingly use these malicious variants, potentially leading to reputational damage and security breaches.

How To Fix

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

npm uninstall mutr-sds-bata

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 measure, avoid using the mutr-sds-bata package and consider using alternative packages that provide similar functionality without the associated risks. Regularly monitor your package dependencies for any updates or vulnerabilities.

Conclusion

The mutr-sds-bata package poses a significant security risk due to its malicious code injection. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities, ensuring the safety and integrity of your applications.

See every vulnerability recorded for mutr-sds-bata →

Share this vulnerability

FAQ

mutr-sds-bata is an npm package linked to a malicious campaign that alters package metadata and publishes variants to the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and integrity.

You should uninstall the package immediately using 'npm uninstall mutr-sds-bata' and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall mutr-sds-bata

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