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

madan-poke42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-158981: Malicious code in madan-poke42 (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-poke42 is part of a broader set of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in madan-poke42 originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This activity not only pollutes the npm registry but also compromises the security and reliability of applications that depend on these packages.

How To Fix

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

npm uninstall madan-poke42

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-poke42 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.

Conclusion

The madan-poke42 package poses a significant threat to npm users due to its malicious code that alters package metadata and floods the registry with harmful variants. It is crucial to remove this package from your projects and adopt best practices for dependency management to safeguard your applications.

See every vulnerability recorded for madan-poke42 →

Share this vulnerability

FAQ

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

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

Using madan-poke42 can lead to security vulnerabilities, including the potential exposure of sensitive data and the compromise of your application's integrity.

There is no patch available for madan-poke42. The recommended action is to uninstall the package and replace it with a secure alternative.

Regularly audit your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall madan-poke42

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