Malicious Code Injection in putri-gudeg83-breki Package
Summary
MAL-2025-74983: Malicious code in putri-gudeg83-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-gudeg83-breki package is part of the npm ecosystem, primarily used for various JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish itself under random names, which can severely impact developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being associated with a token reward campaign that exploits npm's publishing system. It contains scripts designed to automatically generate and publish numerous derivative packages with altered package.json files. This results in the removal of private flags, changes to version numbers, and the creation of random package names, ultimately leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-gudeg83-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-gudeg83-breki package and monitor your project for any dependencies that may have inadvertently included it. Regularly check your package-lock.json file for any signs of this malicious package.
Conclusion
The putri-gudeg83-breki package poses a significant threat due to its malicious code that modifies package files and repopulates the npm registry with harmful derivatives. It is essential to remove this package from your projects and monitor your dependencies regularly to maintain security.
See every vulnerability recorded for putri-gudeg83-breki →
FAQ
It is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the package immediately using 'npm uninstall putri-gudeg83-breki' and check for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
