Malicious Code Injection in okta-rangi33-breki Package - npm Vulnerability
Summary
MAL-2025-74802: Malicious code in okta-rangi33-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-rangi33-breki package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the okta-rangi33-breki package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts included in this package are designed to continuously republish variants, leading to pollution of the npm registry and potential exploitation of developers' environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-rangi33-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 remove the okta-rangi33-breki package from your project by executing the command: npm uninstall okta-rangi33-breki. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The okta-rangi33-breki package has been identified as containing malicious code that can compromise your project. It is crucial to take immediate action by updating or removing the package to mitigate potential risks. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for okta-rangi33-breki →
FAQ
The okta-rangi33-breki package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
This vulnerability can lead to the pollution of the npm registry and may expose your project to further risks if the package is used.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.
Regularly updating your dependencies and using tools like Vulert can help monitor for vulnerabilities and ensure your project remains secure.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a safe version is available.
