Malicious Code Injection in okta-buburayam43-breki Package
Summary
MAL-2025-74776: Malicious code in okta-buburayam43-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-buburayam43-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that exploits npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The malicious payload can affect developers by misleading them into using compromised packages, which may introduce security risks or unstable code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-buburayam43-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, avoid using the okta-buburayam43-breki package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit.
Conclusion
The okta-buburayam43-breki package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action to remove this package and monitor for any further vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software projects.
See every vulnerability recorded for okta-buburayam43-breki →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Using this package can lead to the introduction of malicious code into your application, potentially compromising security and stability.
Regularly audit your dependencies, use tools like npm audit, and stay informed about known vulnerabilities in the packages you use.
Immediately uninstall the package and review your project's dependencies for any other potentially compromised packages.
