Malicious Code Detected in putri-mie13-wekto: A Threat to npm Ecosystem
Summary
MAL-2025-89713: Malicious code in putri-mie13-wekto (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-mie13-wekto' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'putri-mie13-wekto' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to security risks for applications that inadvertently rely on these compromised packages. The origin of this issue is linked to the broader tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-mie13-wekto
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 workaround, you can avoid using the 'putri-mie13-wekto' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall putri-mie13-wekto.
Conclusion
The 'putri-mie13-wekto' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with compromised variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for putri-mie13-wekto →
FAQ
The malicious code modifies the package.json file to remove private flags and changes version numbers, allowing it to republish variants that can pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, it can help identify affected packages.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Always keep your packages updated to the latest secure versions.
You should uninstall the package immediately using the command: npm uninstall putri-mie13-wekto, and check for any other affected packages in your project.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.