Critical Malicious Code Vulnerability in fabric-asset-pipeline Package

fabric-asset-pipeline Updated 29 Sep 2026

Summary

28/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17224: Malicious code in fabric-asset-pipeline (npm). Affects fabric-asset-pipeline versions 1.0.0 – 1.0.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

fabric-asset-pipeline is an npm package designed to serve as an asset loader bridge for web applications. It is intended to streamline the management of assets such as images, stylesheets, and scripts. However, a serious vulnerability has been discovered in version 1.0.0, where malicious code is executed during the installation process, compromising user security.

Vulnerability Detail

The vulnerability originates from a postinstall hook in the fabric-asset-pipeline package that executes an obfuscated index.js file. This file contains malicious functions that steal Minecraft account credentials from various sources, including the official Minecraft launcher and other third-party launchers. The stolen data, including usernames and access tokens, is sent to a hardcoded external server via HTTP POST requests. The obfuscation techniques used make it difficult to detect the malicious behavior, posing a significant risk to users who install this package.

How To Fix

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

npm uninstall fabric-asset-pipeline

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, avoid using the fabric-asset-pipeline package until you can ensure that you are using a safe version. Additionally, consider using alternative asset management packages that do not have known vulnerabilities.

Conclusion

The fabric-asset-pipeline package has a critical vulnerability that allows malicious code to steal sensitive information. Users are strongly advised to update to the latest version and monitor their dependencies to prevent future risks.

See every vulnerability recorded for fabric-asset-pipeline →

Share this vulnerability

FAQ

The malicious code is designed to steal Minecraft account credentials and send them to an external server.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

Immediately update to the patched version (1.0.1) using the command 'npm install fabric-asset-pipeline@1.0.1' to mitigate the risk.

Regularly monitor your dependencies using tools like Vulert and keep them updated to the latest secure versions.

Failure to address this vulnerability may lead to unauthorized access to your Minecraft accounts and potential data breaches.

How To Fix

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

npm uninstall fabric-asset-pipeline

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