Malicious Code Injection in putra-gaplek28-breki Package
Summary
MAL-2025-74922: Malicious code in putra-gaplek28-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 putra-gaplek28-breki package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a larger campaign that aims to manipulate the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in the putra-gaplek28-breki package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for unauthorized access to sensitive data and the proliferation of malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-gaplek28-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-gaplek28-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The putra-gaplek28-breki package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial to remove this package and monitor your applications for vulnerabilities to maintain security.
See every vulnerability recorded for putra-gaplek28-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to unauthorized changes in your package.json file, potentially exposing your application to security risks.
You should uninstall the package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
