Malicious Code Vulnerability in fabian Package: npm Exploit

fabian Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171181: Malicious code in fabian (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fabian package is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in the fabian package originates from its involvement in the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to unauthorized access and manipulation of project dependencies, posing significant security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall fabian

If 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 remove the fabian package from your project by executing the command: 'npm uninstall fabian'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The fabian package has been identified as a vector for malicious code within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your projects by updating or removing affected packages.

See every vulnerability recorded for fabian →

Share this vulnerability

FAQ

The fabian package is a JavaScript library available on npm, used for various development tasks. However, it has been compromised and is associated with malicious activities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify if your project is affected by this vulnerability.

Using the compromised fabian package can lead to unauthorized access to your project, manipulation of dependencies, and potential exposure of sensitive information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot update the package immediately, consider removing it from your project as a temporary measure to prevent any malicious code from executing.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall fabian

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback