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

madan-poke17 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158953: Malicious code in madan-poke17 (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

madan-poke17 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with numerous derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, ultimately compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in madan-poke17 stems from its inclusion in a malicious package ecosystem that employs scripts to alter package.json files. This manipulation removes private flags, modifies version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include the pollution of the npm registry, potential security risks for developers using these packages, and the undermining of trust in the npm ecosystem.

How To Fix

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

npm uninstall madan-poke17

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 madan-poke17 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities.

Conclusion

The madan-poke17 package poses a significant threat to the npm ecosystem due to its malicious nature and the potential for widespread impact. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize monitoring tools to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for madan-poke17 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and undermining the integrity of your project's dependencies.

You should uninstall the madan-poke17 package immediately using 'npm uninstall madan-poke17' and review your other dependencies for any related issues.

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

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

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