Malicious Code Injection in okta-kepok86-breki: A Threat to npm Packages
Summary
MAL-2025-74784: Malicious code in okta-kepok86-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 package 'okta-kepok86-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a broader campaign that exploits npm's publishing capabilities to generate and distribute malicious software. The primary function of this package is to serve as a token reward mechanism, but it has been compromised to perform harmful actions.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'okta-kepok86-breki' package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potentially damaging the reputation of developers. The malicious code is designed to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-kepok86-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include 'okta-kepok86-breki' in your package.json or lock file. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'okta-kepok86-breki' package has been identified as malicious, posing significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for okta-kepok86-breki →
FAQ
The malicious code can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and reputation.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed 'okta-kepok86-breki', you should uninstall it immediately using 'npm uninstall okta-kepok86-breki' and check for any other compromised packages.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
Using compromised packages can lead to security breaches, loss of data integrity, and damage to your project's reputation, making it crucial to regularly audit your dependencies.
