Malicious Code Vulnerability in okta-dodol71-breki Package
Summary
MAL-2025-74778: Malicious code in okta-dodol71-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-dodol71-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 exploits npm's publishing capabilities to inflate developer reputation scores through the creation of derivative packages.
Vulnerability Detail
The vulnerability in the okta-dodol71-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these malicious packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-dodol71-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-dodol71-breki package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The okta-dodol71-breki package poses a significant risk due to its malicious nature, which modifies package metadata and floods the npm registry with harmful derivatives. Developers are advised to remove this package and utilize trusted alternatives to maintain the security and integrity of their applications.
See every vulnerability recorded for okta-dodol71-breki →
FAQ
The okta-dodol71-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
Using the okta-dodol71-breki package can compromise your application's integrity and expose it to potential security risks, including the introduction of malicious code.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply analyzing your package-lock.json file, Vulert can provide real-time alerts. You can also check your application using the Vulert playground at Vulert Scanner.
If you have already included the okta-dodol71-breki package in your project, you should uninstall it immediately and replace it with a trusted alternative.
There is no patch for the okta-dodol71-breki package since it is a malicious package. The best course of action is to remove it from your project.
