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

muda-poke14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

muda-poke14 is an npm package that is part of a broader token reward campaign associated with the tea.xyz protocol. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in muda-poke14 stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names, which can lead to reputation inflation for malicious actors. This behavior not only pollutes the npm registry but also compromises the integrity of the packages available to developers, potentially leading to security risks and loss of trust in the ecosystem.

How To Fix

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

npm uninstall muda-poke14

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 workaround, consider using the following command to uninstall the affected package: npm uninstall muda-poke14. Additionally, monitor your package-lock.json file for any unauthorized changes and ensure that your project dependencies are secure.

Conclusion

The muda-poke14 package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for any further vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for muda-poke14 →

Share this vulnerability

FAQ

The impact includes potential pollution of the npm registry and compromised integrity of the packages, which can lead to security risks for developers and users.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed muda-poke14, it is crucial to uninstall it immediately and review your project dependencies for any other malicious packages.

Currently, there are no known patches for muda-poke14. The best course of action is to remove the package and monitor for updates.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall muda-poke14

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