Malicious Code Injection in okta-rangi35-breki Package - npm Vulnerability
Summary
MAL-2025-122342: Malicious code in okta-rangi35-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The okta-rangi35-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 floods the npm registry with harmful packages, aimed at manipulating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the okta-rangi35-breki package originates from its involvement in the tea.xyz token reward campaign. This package contains malicious scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. The scripts continuously republish these variants, 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 okta-rangi35-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 okta-rangi35-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The okta-rangi35-breki package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and monitoring their dependencies.
See every vulnerability recorded for okta-rangi35-breki →
FAQ
The okta-rangi35-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 injection of malicious code into your application, potentially compromising its security and integrity.
If you have installed the okta-rangi35-breki package, you should uninstall it immediately and check for any alternative packages that are safe to use.
You can use tools like Vulert, which monitors your package-lock.json file for 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.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.