# MAL-2026-3776: Malicious code in typography-stylecss (npm)


- **Type:** Malicious package
- **Package:** `typography-stylecss` (npm)
- **Published:** 14 May 2026

## What is MAL-2026-3776?

MAL-2026-3776 is a malicious package in typography-stylecss, published on 14 May 2026. 

### Official description

The package impersonates the legitimate @tailwindcss/typography plugin: README, src/index.js, src/utils.js, and src/styles.js are copied verbatim from the Tailwind Labs plugin, and peerDependencies lists tailwindcss to reinforce the masquerade, but the package is published under the unrelated name typography-stylecss. Appended to src/index.js after the legitimate `module.exports = plugin.withOptions(...)` is an obfuscator.io-style payload (hex-named identifiers _0x168f6b, _0x3fc27f, etc., with a rotated string table _0x5975). Decoded string-table fragments include platform branching ('win32', 'windows', 'agent-linux-') and a URL path template `/agents/<deploymentHash>` built against a base URL read from a `__SSTAR_API_BASE` global, consistent with downloading a platform-specific agent binary and executing it. Because this code sits at module top level, it fires on `require('typography-stylecss')` / `import 'typography-stylecss'` — exactly the usage the cloned README instructs developers to add to their `tailwind.config.js`. Any build or dev server that loads the Tailwind config will trigger the dropper, which fetches and runs an attacker-controlled native binary on the installer's machine.

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

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-3776 is a malicious package: typography-stylecss (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-3776/ (Markdown: https://insights.sbomify.com/MAL-2026-3776/index.md)
```

## Sources

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

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