Malicious Code Injection in putri-kupat35-breki Package
Summary
MAL-2025-75002: Malicious code in putri-kupat35-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 putri-kupat35-breki package is part of the npm ecosystem and appears to be involved in the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the putri-kupat35-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential misuse of developer reputation systems. The ramifications include loss of trust in the npm ecosystem and potential exploitation of developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-kupat35-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 workaround, you can avoid using the putri-kupat35-breki package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a trusted alternative.
Conclusion
The putri-kupat35-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities.
See every vulnerability recorded for putri-kupat35-breki →
FAQ
It is an npm package involved in a token reward campaign that has been identified to contain malicious code.
The code modifies your package.json file and can lead to the publication of unauthorized packages, affecting your project's integrity.
You should remove the putri-kupat35-breki package from your project and monitor for any updates or patches.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
