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

madan-poke46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158985: Malicious code in madan-poke46 (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 madan-poke46 package is part of a broader ecosystem within npm, often associated with token reward campaigns. These packages are designed to manipulate the npm registry by automatically generating and publishing numerous derivative packages. This behavior is intended to inflate developer reputation scores for rewards, making it a target for malicious activity.

Vulnerability Detail

The vulnerability in madan-poke46 stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall madan-poke46

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, avoid using the madan-poke46 package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file for any malicious packages.

Conclusion

The madan-poke46 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their applications.

See every vulnerability recorded for madan-poke46 →

Share this vulnerability

FAQ

Madan-poke46 is an npm package that has been identified as containing malicious code designed to manipulate the npm registry.

The vulnerability can lead to the introduction of compromised packages into your application, potentially causing security breaches and instability.

You can use Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed madan-poke46, uninstall it immediately using 'npm uninstall madan-poke46' and check for any other affected packages.

Yes, Vulert provides real-time monitoring for open-source vulnerabilities using just your package-lock.json file, making it easy to stay informed.

How To Fix

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

npm uninstall madan-poke46

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