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

muda-poke33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160768: Malicious code in muda-poke33 (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

The package muda-poke33 is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores within the tea protocol, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in muda-poke33 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and republishing of numerous variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the broader trend of malicious packages flooding npm, specifically targeting developers involved in the tea.xyz token reward scheme.

How To Fix

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

npm uninstall muda-poke33

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-poke33 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to scan your package-lock.json for vulnerabilities.

Conclusion

The muda-poke33 package poses a significant risk due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their applications remain secure.

See every vulnerability recorded for muda-poke33 →

Share this vulnerability

FAQ

muda-poke33 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should remove the muda-poke33 package from your project and monitor for any malicious activity.

You can use the Vulert playground at Vulert Scanner to check your application without needing to sign up.

Yes, Vulert can monitor and alert in real-time for open-source vulnerabilities using just your package-lock.json.

How To Fix

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

npm uninstall muda-poke33

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