Which versions of typography-stylecss are malicious?

The following npm versions of typography-stylecss are flagged malicious: 0.7.4. Treat any of these as compromised.

How do I remediate typography-stylecss if I installed it?

typography-stylecss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed typography-stylecss — how do I know if it already compromised me?

If typography-stylecss 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.

Is typography-stylecss part of a known attack campaign?

Yes — typography-stylecss is associated with the IN-MAL-2026-002713 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find typography-stylecss across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for typography-stylecss (version 0.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typography-stylecss across your stack and pipelines.

Malicious package

typography-stylecssnpm

Malicious code in typography-stylecss (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3776

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall typography-stylecss

What this malware does

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.

Malicious versions

1 flagged

0.7.4

Indicators of compromise (SHA-256)

4eeb50f69746fd21696baaa7d3534bbd22489edb037742ca591d49ca88981f70

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for typography-stylecss (version 0.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typography-stylecss across your stack and pipelines.
If you installed it — respond
typography-stylecss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If typography-stylecss 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 typography-stylecss 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

No. typography-stylecss on npm has been identified as a malicious package (version 0.7.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002713

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typography-stylecss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring