Malicious Code Injection in putri-bika1-breki Package: A Threat to npm Users
Summary
MAL-2025-74965: Malicious code in putri-bika1-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-bika1-breki package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on npm packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the putri-bika1-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package. Users may unknowingly install these malicious packages, leading to unauthorized access or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-bika1-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-bika1-breki package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time. 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 putri-bika1-breki package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. Users are advised to uninstall this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for putri-bika1-breki →
FAQ
The putri-bika1-breki package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file and continuously republishes variants, which can lead to security vulnerabilities and potential data breaches.
You should uninstall the putri-bika1-breki package immediately and monitor your project for any unusual behavior or vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
