Malicious Code Injection in madan-poke43: A Threat to npm Ecosystem
Summary
MAL-2025-158982: Malicious code in madan-poke43 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
madan-poke43 is an npm package that appears to be part of a larger campaign aimed at exploiting the npm registry. This package, like others in the tea.xyz token reward initiative, is designed to manipulate package publishing processes. It generates and publishes derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. The presence of malicious code in this package poses a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in madan-poke43 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The ramifications of this vulnerability include potential reputational damage for developers, compromised project integrity, and the risk of inadvertently using malicious packages in production environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall madan-poke43If 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 madan-poke43 and any other packages that are part of 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 in your dependencies.
Conclusion
The discovery of malicious code in the madan-poke43 package highlights the ongoing risks associated with open-source software. Developers must remain vigilant, regularly update their dependencies, and utilize tools like Vulert to safeguard their projects against vulnerabilities. By taking proactive measures, the integrity of the npm ecosystem can be maintained.
See every vulnerability recorded for madan-poke43 →
FAQ
madan-poke43 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.
The vulnerability can lead to the introduction of malicious packages into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall madan-poke43' and review your project's dependencies for any other malicious packages.
Yes, regularly update your dependencies, monitor your package-lock.json file, and use tools like Vulert to detect vulnerabilities in real-time.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check for vulnerabilities without any installation or signup.
