Malicious Code Injection in abedghaleb Package: npm Vulnerability Overview
Summary
MAL-2025-170639: Malicious code in abedghaleb (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 abedghaleb package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automatically generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea protocol.
Vulnerability Detail
The vulnerability in the abedghaleb package stems from its inclusion in 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, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is executed through autopublish scripts that are embedded within the package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abedghalebIf 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 abedghaleb package and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The abedghaleb package poses a significant risk due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications remain secure.
See every vulnerability recorded for abedghaleb →
FAQ
The abedghaleb package is an npm package that has been identified as part of a malicious campaign aimed at exploiting npm's publishing features.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your application and potentially introducing malicious code.
You should uninstall the abedghaleb package immediately using the command: npm uninstall abedghaleb.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
