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

muda-poke38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160773: Malicious code in muda-poke38 (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-poke38 is an npm package that is part of a broader campaign aimed at manipulating the npm registry for token rewards. It is designed to provide developers with tools or functionalities, but it has been compromised to include malicious scripts that alter its behavior and integrity. The package is part of a series of similar packages that have been identified as harmful, primarily due to their ability to publish derivative versions with altered metadata.

Vulnerability Detail

The vulnerability in muda-poke38 originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish itself, polluting the npm registry. The malicious payload can lead to significant ramifications, including the potential for developers to unknowingly use compromised packages, which can further propagate the malicious code across projects.

How To Fix

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

npm uninstall muda-poke38

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 muda-poke38 and any other packages that are part of the same malicious campaign. Regularly audit your project's dependencies and remove any suspicious packages. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The muda-poke38 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects remain secure.

See every vulnerability recorded for muda-poke38 →

Share this vulnerability

FAQ

muda-poke38 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability allows the package to alter its metadata and republish itself, which can lead to the inclusion of malicious code in your project.

You should uninstall the package immediately using 'npm uninstall muda-poke38' and check for any other affected packages.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall muda-poke38

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