Malicious Code Injection in madan-poke33: A Threat to npm Users

madan-poke33 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158971: Malicious code in madan-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package madan-poke33 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of madan-poke33 lies in its ability to modify the package.json file, removing private flags and altering version numbers, which can lead to further exploitation and pollution of the npm registry.

Vulnerability Detail

The vulnerability in madan-poke33 originates from its inclusion in a malicious campaign that floods the npm ecosystem with harmful packages. The payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to the proliferation of untrusted packages in the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages in their projects.

How To Fix

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

npm uninstall madan-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 measure, you can avoid using madan-poke33 and any other packages associated with the tea.xyz campaign. Regularly audit your package dependencies using tools like npm audit to identify and remove any malicious packages.

Conclusion

The madan-poke33 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package.json files and proliferates untrusted packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for madan-poke33 →

Share this vulnerability

FAQ

Madan-poke33 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of harmful packages.

The vulnerability can lead to the introduction of untrusted packages in your project, potentially compromising the security and integrity of your application.

You should uninstall the package immediately using the command npm uninstall madan-poke33 and audit your project for any other malicious dependencies.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

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 madan-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