Malicious Code Injection in putri-lodeh40-miaww: A Threat to npm Ecosystem
Summary
MAL-2025-89693: Malicious code in putri-lodeh40-miaww (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 'putri-lodeh40-miaww' 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. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'putri-lodeh40-miaww' originates from its malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-lodeh40-miawwIf 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, avoid using the 'putri-lodeh40-miaww' package and any other packages associated with the tea.xyz token reward campaign. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'putri-lodeh40-miaww' package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and repopulates the registry with tainted variants. It is essential for developers to take immediate action to remove this package and implement best practices for dependency management to safeguard their projects.
See every vulnerability recorded for putri-lodeh40-miaww →
FAQ
The malicious code can compromise your project's integrity by modifying essential files and introducing untrusted packages into your environment.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall putri-lodeh40-miaww' and review your project's dependencies for any other malicious packages.
Yes, consider using well-established packages that serve similar purposes but do not have a history of malicious behavior.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories related to your packages.
