Malicious Code Injection in muda-poke21: A Threat to npm Ecosystem

muda-poke21 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160755: Malicious code in muda-poke21 (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

muda-poke21 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate certain functionalities within the npm ecosystem, but it has been compromised. The package is known for generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This behavior makes it susceptible to exploitation, leading to potential security risks for users and developers relying on it.

Vulnerability Detail

The vulnerability in muda-poke21 stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This malicious payload allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall muda-poke21

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 remove the muda-poke21 package from your project by running the following command: npm uninstall muda-poke21. This will prevent any malicious activity associated with the package until a secure version is available.

Conclusion

The muda-poke21 package has been identified as containing malicious code that poses a significant threat to the npm ecosystem. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for muda-poke21 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages the software, leading to potential security risks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you are using muda-poke21, it is crucial to update the package to a secure version or remove it from your project.

Failing to address this vulnerability can lead to compromised security, data integrity issues, and potential exploitation of your application.

Check the npm registry for any available patches or updates for muda-poke21 to ensure you are using a secure version.

How To Fix

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

npm uninstall muda-poke21

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