tailwind-typography-stylenpm
tailwind-typography-style is a confirmed malicious npm package (MAL-2026-5854) that typosquats a legitimate package to trick installs (malicious version 0.5.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tailwind-typography-style (npm)
What this malware does
The package impersonates @tailwindcss/typography by name and ships a verbatim copy of tailwindlabs/tailwindcss-typography's src/ tree (index.js, styles.js, utils.js) so it appears functional. After the legitimate module.exports = plugin.withOptions(...) block, src/index.js appends a custom string-shuffle cipher (the _$_1e42 IIFE and sfL decoder) that decodes the strings require, module, and constructor, retrieves the Function constructor via sfL[EKc], compiles a deobfuscated body string into a function (var xBg=dgC(Apa,sfL(joW)); var pYd=xBg(sfL('o B%v[Raca...'));), and immediately invokes it (Tgw(2509)). Node's require is stashed on global under a deobfuscated key so the dynamically-created function has full access to the filesystem, network, and child_process. Any project that does require('tailwind-typography-style') (or imports it through a Tailwind config) executes attacker-controlled code at module load while the legitimate plugin API masks the behavior. Two layers of custom Fisher–Yates string-shuffle obfuscation are used to hide payload contents from static review — there is no legitimate reason for a Tailwind CSS plugin to perform runtime code generation.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-typography-style (version 0.5.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-typography-style across your stack and pipelines.
If you installed it — respond
tailwind-typography-style is a typosquat — you almost certainly intended a legitimately-named package. Remove tailwind-typography-style, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If tailwind-typography-style was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tailwind-typography-style before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tailwind-typography-style-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.