Malicious Code Injection in ogi-miebogor72-breki: A Threat to npm Packages
Summary
MAL-2025-74744: Malicious code in ogi-miebogor72-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 package 'ogi-miebogor72-breki' 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 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 pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in 'ogi-miebogor72-breki' originates from its association with the tea.xyz token reward campaign, which has been known to distribute malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the affected package but also poses a risk to the broader npm ecosystem by enabling the continuous republishing of these variants, thereby polluting the registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ogi-miebogor72-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 workaround, consider using a package-lock.json file to lock down your dependencies and prevent the installation of malicious packages. You can also monitor your dependencies using tools like Vulert, which provides real-time alerts for open-source vulnerabilities without requiring code access. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The ogi-miebogor72-breki package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for ogi-miebogor72-breki →
FAQ
The ogi-miebogor72-breki package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.
You should uninstall the ogi-miebogor72-breki package immediately and check for any other potentially malicious packages in your project.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and only install packages from trusted sources.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
