Malicious Code Injection in okta-oncom98-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74797: Malicious code in okta-oncom98-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-oncom98-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package appears to be linked to a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'okta-oncom98-breki' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which utilizes scripts to automate the creation and publication of these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-oncom98-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-oncom98-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended dependencies that may arise from using other packages.
Conclusion
The 'okta-oncom98-breki' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for okta-oncom98-breki →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with harmful packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall okta-oncom98-breki' and check for any other affected packages.
Yes, consider researching and using other reputable packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
