Malicious Code Injection in putri-serabi20-breki: A Threat to npm Packages
Summary
MAL-2025-75051: Malicious code in putri-serabi20-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-serabi20-breki' is part of a larger ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The intent behind this manipulation is to inflate developer reputation scores for rewards associated with the tea protocol. However, this behavior poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'putri-serabi20-breki' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The origin of this vulnerability is linked to the broader malicious activity associated with the tea.xyz token reward campaign, which has been flagged by security tools like Amazon Inspector.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-serabi20-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, you can avoid using the 'putri-serabi20-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json file.
Conclusion
The 'putri-serabi20-breki' package poses a significant threat due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for putri-serabi20-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json and repackages itself, which can lead to security vulnerabilities in applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
You should uninstall the package immediately using 'npm uninstall putri-serabi20-breki' and look for alternative packages.
Yes, you should look for other npm packages that offer similar functionality without the associated risks. Always verify the package's reputation before installation.
Vulert uses your package-lock.json to monitor for vulnerabilities in your open-source dependencies and alerts you in real-time, ensuring your application remains secure.
