Malicious Code Injection in putri-ronde41-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75042: Malicious code in putri-ronde41-breki (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-ronde41-breki' is part of the npm ecosystem and appears to be linked to a token reward campaign associated with the tea.xyz protocol. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores. However, it has been identified as malicious due to its capability to modify package metadata and republish variants, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'putri-ronde41-breki' originates from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to a significant increase in unwanted packages in the npm registry, affecting developers and users by complicating package management and potentially introducing security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-ronde41-brekiIf 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, avoid using the 'putri-ronde41-breki' package in your projects. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of this malicious package.
Conclusion
The discovery of malicious code in the 'putri-ronde41-breki' package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and utilize tools like Vulert for ongoing monitoring. By staying informed and proactive, the risks associated with such vulnerabilities can be mitigated.
See every vulnerability recorded for putri-ronde41-breki →
FAQ
The malicious code can lead to the pollution of the npm registry with unwanted packages, complicating package management for developers.
You can use Vulert to monitor your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall putri-ronde41-breki' and check for any dependencies that may be affected.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize risks.
Signs include unexpected changes in your package-lock.json file, the presence of unknown packages, or unusual behavior in your application.
