Malicious Code Injection in wibowo-tek9-breki: A Threat to npm Ecosystem
Summary
MAL-2025-76282: Malicious code in wibowo-tek9-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 wibowo-tek9-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby undermining the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in wibowo-tek9-breki originates from its association with a token reward campaign that has led to the creation of numerous malicious packages. These packages contain scripts designed to automatically modify package.json files, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wibowo-tek9-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 wibowo-tek9-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The wibowo-tek9-breki package poses a significant threat to the npm ecosystem due to its malicious code that modifies package configurations and floods the registry. It is crucial for developers to take immediate action by uninstalling the package and monitoring their dependencies for vulnerabilities.
See every vulnerability recorded for wibowo-tek9-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.
You should uninstall the package immediately using the command: npm uninstall wibowo-tek9-breki.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
Failing to address this vulnerability could lead to security risks, including the exposure of sensitive data and the compromise of your application.
