Malicious Code Injection in muda-poke15: A Threat to npm Ecosystem
Summary
MAL-2025-160748: Malicious code in muda-poke15 (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
muda-poke15 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various automated processes. However, it has been identified as a malicious package that can compromise the integrity of the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability in muda-poke15 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall muda-poke15If 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 prevent the installation of the muda-poke15 package by using the following command: npm uninstall muda-poke15. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The muda-poke15 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to stay informed about such vulnerabilities and take necessary actions to protect their applications. Regular updates and monitoring can help mitigate these risks.
See every vulnerability recorded for muda-poke15 →
FAQ
The impact includes potential pollution of the npm registry, compromised application integrity, and risks associated with dependency confusion.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
If you cannot update the package, consider removing it from your project and replacing it with a safer alternative.
The malicious payload modifies the package.json file to remove private flags and changes version numbers, allowing the package to be republished under random names.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.
