Malicious Code Injection in putra-tahu40-miaww: A Threat to npm Packages
Summary
MAL-2025-89611: Malicious code in putra-tahu40-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 'putra-tahu40-miaww' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'putra-tahu40-miaww' originates from its design to include autopublish scripts that modify 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 to pollute the npm registry. This behavior can lead to reputation inflation for malicious actors and compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-tahu40-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 workaround, you can remove the 'putra-tahu40-miaww' package from your project by executing: npm uninstall putra-tahu40-miaww. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The 'putra-tahu40-miaww' package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to update or remove this package to protect their applications from potential threats. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for putra-tahu40-miaww →
FAQ
The malicious code modifies package metadata and publishes numerous derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package to mitigate the risk until a secure version is released.
Yes, the vulnerability can lead to reputation inflation for malicious actors and compromise the integrity of the npm registry, affecting developers and users.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring your application remains secure.
