Malicious Code Injection in okta-ragi69-breki Package - npm Vulnerability
Summary
MAL-2025-74800: Malicious code in okta-ragi69-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 okta-ragi69-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability stems from the okta-ragi69-breki package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-ragi69-breki
If 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 okta-ragi69-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The okta-ragi69-breki package poses a significant risk due to its association with malicious activities in the npm ecosystem. Developers are advised to remove this package and monitor their applications for any signs of compromise. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for vulnerabilities.
See every vulnerability recorded for okta-ragi69-breki →
FAQ
The okta-ragi69-breki package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
If your application uses the okta-ragi69-breki package, it may be at risk of being compromised due to the malicious scripts embedded in the package.
You should immediately remove the okta-ragi69-breki package from your project and monitor your application for any unusual behavior.
Yes, tools like Vulert can help monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.