Malicious Code Injection in muda-poke20: A Threat to npm Users
Summary
MAL-2025-160754: Malicious code in muda-poke20 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package muda-poke20 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript libraries and applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages with altered attributes.
Vulnerability Detail
The vulnerability in muda-poke20 originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. These actions lead to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muda-poke20If 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-poke20 package until a fixed version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.
Conclusion
The muda-poke20 package poses a significant risk due to its malicious code designed to manipulate package attributes and pollute the npm registry. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for muda-poke20 →
FAQ
The vulnerability involves malicious code that modifies package attributes and republish variants to pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Using compromised packages can lead to security vulnerabilities, data breaches, and damage to your application's integrity.
Regularly audit your dependencies using tools like npm audit, and stay updated on security advisories related to the packages you use.
Remove the package from your project and update to a safe alternative. Ensure to review your project for any potential security issues.
