Malicious Code Injection in maman-martabak8-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-105549: Malicious code in maman-martabak8-ruro (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
The package 'maman-martabak8-ruro' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the developers using these packages.
Vulnerability Detail
The vulnerability in 'maman-martabak8-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious code can also facilitate further exploitation by allowing unauthorized access to sensitive data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maman-martabak8-ruroIf 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 'maman-martabak8-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'maman-martabak8-ruro' package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for maman-martabak8-ruro →
FAQ
The main risk is the injection of malicious code that can compromise the integrity of your application and the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately and look for secure alternatives.
Yes, you should research and identify alternative packages that provide similar functionality without the associated risks.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
