Critical Malicious Code Vulnerability in fabric-loader-core Package

fabric-loader-core Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17306: Malicious code in fabric-loader-core (npm). Affects fabric-loader-core versions 1.0.0. 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

fabric-loader-core is an npm package designed as a native asset loader bridge for Fabric mod environments. It is intended to facilitate the integration of assets in Minecraft modding. However, this package has been found to contain a significant security vulnerability that allows for the execution of arbitrary code during installation, posing severe risks to users.

Vulnerability Detail

The vulnerability originates from the package's postinstall hook, which executes index.js. This script performs an HTTPS GET request to a hardcoded malicious server (https://fabric-npm.gm-service.xyz/p) and directly executes the response using vm.runInContext. This means that any code returned by the server runs with full Node.js privileges on the installer's machine. The implications of this vulnerability are severe, including potential credential theft, unauthorized persistence, and lateral movement within networks. The package's misleading name and purpose further complicate the issue, as it disguises its malicious intent.

How To Fix

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

npm uninstall fabric-loader-core

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 installing the fabric-loader-core package until a secure version is available. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The fabric-loader-core package contains a critical vulnerability that allows for the execution of malicious code during installation. Users are advised to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for fabric-loader-core →

Share this vulnerability

FAQ

The vulnerability allows malicious code to be executed on the user's machine during the installation of the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

The risks include credential theft, unauthorized access, and potential control over the user's machine.

The best mitigation is to avoid using the fabric-loader-core package until a patched version is released.

Regularly check for updates in your package manager and consider using tools like Vulert for real-time monitoring.

How To Fix

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

npm uninstall fabric-loader-core

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