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

muda-poke4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160775: Malicious code in muda-poke4 (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-poke4 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used for various development purposes. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem by generating and publishing derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in muda-poke4 originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in developers unknowingly using compromised packages, leading to potential security risks in their applications.

How To Fix

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

npm uninstall muda-poke4

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-poke4 package from your project by executing the command: 'npm uninstall muda-poke4'. This will prevent any malicious code from executing until a patched version is available.

Conclusion

The muda-poke4 package has been identified as a threat to the npm ecosystem due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential risks.

See every vulnerability recorded for muda-poke4 →

Share this vulnerability

FAQ

The impact includes potential exposure to malicious code that can alter your project's dependencies and compromise security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

The malicious code modifies package.json files, removes private flags, and generates random package names, leading to the creation of numerous compromised packages.

Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only install packages from trusted sources.

How To Fix

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

npm uninstall muda-poke4

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