Malicious Code Injection in abdushahid Package: npm Vulnerability Overview
Summary
MAL-2025-170635: Malicious code in abdushahid (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 abdushahid package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of abdushahid is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the abdushahid package stems from its inclusion in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. This can result in security risks for developers who unknowingly install these compromised packages, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abdushahidIf 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, you can avoid using the abdushahid package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The abdushahid 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 your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for abdushahid →
FAQ
The abdushahid package is an npm package associated with a token reward campaign that has been compromised to include malicious code.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.
You should uninstall the abdushahid package immediately and check for any other compromised packages in your project.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json 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 needing to sign up.
