Malicious Code Injection in abdulbaguette Package: npm Vulnerability Overview
Summary
MAL-2025-170628: Malicious code in abdulbaguette (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 abdulbaguette 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 the npm registry by flooding it with derivative packages. The primary functionality of abdulbaguette is to serve as a tool for developers, but its integrity has been compromised due to the presence of malicious code that modifies package metadata.
Vulnerability Detail
The vulnerability in the abdulbaguette package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that include scripts designed to automatically publish derivative versions of themselves with altered metadata. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abdulbaguetteIf 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 abdulbaguette package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The abdulbaguette package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for abdulbaguette →
FAQ
Abdulbaguette is an npm package that has been compromised and is part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, leading to potential security risks and pollution of the npm registry.
You should remove the abdulbaguette package from your project immediately and check for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
