Malicious Code Injection in madan-poke11: A Threat to npm Ecosystem

madan-poke11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158947: Malicious code in madan-poke11 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package madan-poke11 is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to numerous malicious packages that flood the npm registry. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in madan-poke11 originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly install malicious packages, risking their applications and data.

How To Fix

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

npm uninstall madan-poke11

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-poke11 and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using the following command to audit your npm packages for vulnerabilities: npm audit.

Conclusion

The madan-poke11 package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package and regularly audit your dependencies to ensure the security of your applications.

See every vulnerability recorded for madan-poke11 →

Share this vulnerability

FAQ

Madan-poke11 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

You should immediately remove the madan-poke11 package from your project and audit your dependencies for any other vulnerabilities.

Yes, tools like Vulert can help you monitor your packages for vulnerabilities in real-time using just the package-lock.json file.

How To Fix

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

npm uninstall madan-poke11

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