# MAL-2026-17224: Malicious code in fabric-asset-pipeline (npm)


- **Type:** Malicious package
- **Package:** `fabric-asset-pipeline` (npm)
- **Published:** 28 Sep 2026

## What is MAL-2026-17224?

MAL-2026-17224 is a malicious package in fabric-asset-pipeline, published on 28 Sep 2026. 

### Official description

fabric-asset-pipeline@1.0.0 declares a postinstall hook that runs index.js on npm install. index.js is heavily obfuscated (obfuscator.io-style rotated string array plus base64+RC4 decoding of identifiers and URLs, with newline/regex anti-formatting hooks) and implements a Minecraft credential stealer: functions stealLauncherAccounts(), stealAltLaunchers(), and readSessionDump() read account credential stores from the official Minecraft launcher (launcher_accounts.json / launcher_profiles.json) as well as Prism/MultiMC, TLauncher, Modrinth, PolyMC, and GDLauncher, plus a session dump from the OS temp directory. Extracted account names, access tokens, and refresh tokens are POSTed via https.request to a hardcoded webhook whose URL is RC4-decoded at runtime. A companion sendInfo() call ships os.hostname(), os.userInfo().username, os.platform()/os.release(), and the recovered Minecraft username to the same endpoint. None of this behavior is part of the package's advertised 'asset loader bridge' purpose, and the obfuscation deliberately conceals both the exfiltration functions and the destination URL.

The OpenSSF Package Analysis project identified 'fabric-asset-pipeline' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

## What should I do about MAL-2026-17224?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17224 is a malicious package: fabric-asset-pipeline (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17224/ (Markdown: https://insights.sbomify.com/MAL-2026-17224/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17224

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17224/
Summaries are generated and may contain mistakes; the official description above is the record.