# MAL-2026-6471: Malicious code in tailwind-color-shades (npm)


- **Type:** Malicious package
- **Package:** `tailwind-color-shades` (npm)
- **Published:** 25 Jun 2026

## What is MAL-2026-6471?

MAL-2026-6471 is a malicious package in tailwind-color-shades, published on 25 Jun 2026. 

### Official description

The package's documented entry point `index.ts` begins with `import './src/bootstrap';`, which causes `src/bootstrap.js` to run whenever the module is required or imported. `src/bootstrap.js` is a custom string-shuffle obfuscator: a function `YWG(x)` deterministically unscrambles opaque string literals (e.g. `YWG('axhscuutcrogycrneotisjlnkdpfqmzovtrwb').substr(0,11)` reconstructs the literal `'constructor'`), then uses `Function.prototype.constructor` to build a `Function` from one shuffled blob, executes it on a second shuffled blob, and invokes the result via `XZs(7942)`. Before invoking the constructed code the bootstrap explicitly re-exposes Node capabilities to it via `global['r']=require; global['m']=module;`, granting the dynamically generated payload full filesystem, child_process, and network access. The package's advertised purpose is straightforward Tailwind color-shade math — a few dozen lines of pure arithmetic — so a hand-rolled string-shuffle obfuscator wrapping `Function`-constructed code at import time has no legitimate purpose. This is the standard supply-chain attack shape: opaque payload, evasion-only obfuscation, automatic execution on consumer import, full Node capability re-export.

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

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-6471 is a malicious package: tailwind-color-shades (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-6471/ (Markdown: https://insights.sbomify.com/MAL-2026-6471/index.md)
```

## Sources

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

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