Malicious Code Injection in ogi-toge47-breki: A Threat to npm Packages
Summary
MAL-2025-74769: Malicious code in ogi-toge47-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 ogi-toge47-breki is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata, inflate developer reputation scores, and ultimately compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in ogi-toge47-breki stems from its inclusion in a series of malicious packages that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the automatic generation and republishing of derivative packages, which pollutes the npm registry and can potentially harm developers relying on legitimate packages. The malicious payload is executed through scripts named auto.js, autopublish.js, autopublish2.js, and autopublish3.js, which are designed to operate without user consent.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ogi-toge47-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 malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your package-lock.json does not include ogi-toge47-breki. You can also use Vulert to monitor your project for vulnerabilities without needing to access the code directly. Visit https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The ogi-toge47-breki package poses a significant threat to the integrity of npm packages due to its malicious behavior. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for ogi-toge47-breki →
FAQ
ogi-toge47-breki 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.
The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising the security of your project.
You should uninstall the package immediately using the command npm uninstall ogi-toge47-breki and check for any other affected packages in your project.
Yes, you can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
