Malicious Code Injection in muda-poke44: A Threat to npm Users

muda-poke44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160780: Malicious code in muda-poke44 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

muda-poke44 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to alter its own metadata and proliferate under various names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in muda-poke44 originates from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the overall trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall muda-poke44

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-poke44 package until a secure version is released. Additionally, you can use the following command to uninstall the package: npm uninstall muda-poke44.

Conclusion

The muda-poke44 package poses a significant risk due to its malicious code that alters package metadata and proliferates under various names. It is essential for developers to take immediate action by updating or removing the package to protect their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for muda-poke44 →

Share this vulnerability

FAQ

muda-poke44 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores by publishing derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your project's package.json, potentially compromising its security and integrity.

If you have installed muda-poke44, it is crucial to update or uninstall the package immediately to mitigate any risks.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories.

How To Fix

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

npm uninstall muda-poke44

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