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

madan-poke41 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158980: Malicious code in madan-poke41 (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 Penetration testing for web, API and mobile 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-poke41 is part of the npm ecosystem and appears to be involved in a token reward campaign associated with tea.xyz. This package is designed to manipulate npm's publishing system, generating numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it poses significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in madan-poke41 originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall madan-poke41

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 prevent the installation of madan-poke41 by using the following command to uninstall it: npm uninstall madan-poke41. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.

Conclusion

The madan-poke41 package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. Users are advised to uninstall the package and monitor their applications for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for madan-poke41 →

Share this vulnerability

FAQ

Madan-poke41 is an npm package that has been identified as malicious, designed to manipulate the npm registry for token reward purposes.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.

You should uninstall madan-poke41 immediately and monitor your package-lock.json for any unauthorized changes.

Yes, 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.

Regularly update your packages, monitor your dependencies using tools like Vulert, and review your package-lock.json for any unauthorized changes.

How To Fix

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

npm uninstall madan-poke41

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