Malicious Code Injection in muda-poke46: A Threat to npm Packages

muda-poke46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160782: Malicious code in muda-poke46 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

muda-poke46 is an npm package that is part of the tea.xyz token reward campaign, which has been associated with malicious activities on the npm registry. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in muda-poke46 originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall muda-poke46

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 muda-poke46 package and check your project for any dependencies that might be using it. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code directly.

Conclusion

The muda-poke46 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert for ongoing monitoring of their projects.

See every vulnerability recorded for muda-poke46 →

Share this vulnerability

FAQ

muda-poke46 is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

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

You should uninstall the package immediately using the command npm uninstall muda-poke46 and check for any other affected dependencies.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code or install additional tools.

Yes, 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 muda-poke46

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