Malicious Code Injection in fayazabdul Package: npm Vulnerability Overview
Summary
MAL-2025-171210: Malicious code in fayazabdul (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The fayazabdul package is part of the npm ecosystem, which is widely used for JavaScript package management. 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 fayazabdul is to serve as a token reward mechanism within the tea.xyz protocol, but it has been compromised to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the fayazabdul package stems from its association with 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 these variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code is designed to execute autopublish scripts that automate the creation and publication of these derivative packages, making it difficult for developers to maintain a clean and secure package ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fayazabdulIf 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, consider removing the fayazabdul package from your project until a secure version is released. You can do this by executing the command: npm uninstall fayazabdul. Additionally, monitor your package-lock.json file for any signs of malicious changes.
Conclusion
The fayazabdul package has been identified as a vector for malicious code injection, posing significant risks to developers and the integrity of the npm ecosystem. It is crucial to take immediate action by updating or removing the package and monitoring your dependencies for any signs of compromise.
See every vulnerability recorded for fayazabdul →
FAQ
The fayazabdul package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing security risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If immediate updates are not possible, consider removing the package as a temporary measure and monitor your dependencies closely.
Detailed information about this vulnerability can be found in the Open Source Vulnerability database and through security advisories related to npm packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
