Malicious Code Injection in putra-kupang52-breki: A Threat to npm Packages
Summary
MAL-2025-74933: Malicious code in putra-kupang52-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 'putra-kupang52-breki' 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 designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'putra-kupang52-breki' originates from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating 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 malicious payload is designed to exploit the npm ecosystem for token rewards, making it a significant threat to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-kupang52-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 'putra-kupang52-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'putra-kupang52-breki' package poses a significant threat due to its malicious code that manipulates npm package metadata. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for putra-kupang52-breki →
FAQ
The package contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can check your package-lock.json file or use npm commands to see if 'putra-kupang52-breki' is listed as a dependency.
Using this package can lead to security vulnerabilities, including unauthorized access to your project and pollution of the npm registry.
Regularly monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.
Immediately uninstall the package and replace it with a secure alternative. Monitor your application for any unusual behavior.
