Malicious Code Injection in muny-boph-dsfs: A Threat to npm Packages

muny-boph-dsfs Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160962: Malicious code in muny-boph-dsfs (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 package 'muny-boph-dsfs' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious behavior of this package poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'muny-boph-dsfs' originates from its association with a token reward campaign that floods the npm registry with malicious packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and compromise the security of dependent projects. The ramifications include potential exposure to further malicious code and a degradation of trust in the npm ecosystem.

How To Fix

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

npm uninstall muny-boph-dsfs

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, you can avoid using the 'muny-boph-dsfs' package and replace it with a trusted alternative. Ensure that your package-lock.json file is monitored for any changes that may introduce vulnerabilities. You can also use tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Conclusion

The 'muny-boph-dsfs' package poses a significant threat due to its malicious behavior aimed at exploiting the npm registry. It is crucial for developers to be vigilant and remove this package from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for muny-boph-dsfs →

Share this vulnerability

FAQ

The 'muny-boph-dsfs' package is an npm package involved in a malicious campaign that floods the npm registry with derivative packages to inflate developer reputation scores.

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

You should uninstall the 'muny-boph-dsfs' package immediately and check your project for any other potentially malicious dependencies.

Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to access the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall muny-boph-dsfs

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