registry / Remote code execution / tailwind-gutenberg-block-zero

tailwind-gutenberg-block-zero

This example demonstrates how to create a modern WordPress block using ESNext (modern JavaScript) and JSX syntax. It showcases the fundamental setup required for block development with a build process powered by `@wordpress/scripts`, which handles all the

This report shows the evidence for tailwind-gutenberg-block-zero@1.0.0, the only known version.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

The package contains a concrete, automatically triggered remote execution chain with stealth and system-modification behavior unrelated to its stated WordPress functionality. Empty Telegram credentials do not mitigate the independently executable remote payload chain.

Static reason

One or more suspicious static signals were detected.

Trigger

Automatic npm `install` lifecycle execution.

Impact

Arbitrary remote code execution, software installation, potential persistence, and host metadata disclosure.

Mechanism

Hidden PowerShell bootstrapper that downloads and runs remote code.

Attack narrative

On npm install, `setup.js` creates a PowerShell script in the temp directory and starts it minimized, detached, and with execution-policy bypass. The script changes current-user policy, installs package-management/runtime tooling when absent, then invokes Deno with unrestricted `-A` permissions to execute JavaScript fetched from a hard-coded HTTP IP. The shipped PowerShell comments explicitly describe a remote eval loop and autorun setup. This behavior is unrelated to the Gutenberg block and is unconsented install-time remote code execution.

AI rationale

Evidence

package.jsonsetup.jssetup.ps1my-tailwind-blocks.phpbuild/block.json%TEMP%\setup.ps1%USERPROFILE%\scoop%LOCALAPPDATA%\Microsoft\WinGet\Packages

Network endpoints3

api.telegram.org/bot${BOT_TOKEN}/sendMessageget.scoop.sh172.94.9.157/v028f8cde892b0b74c8.js

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

`package.json` runs `node setup.js` during npm install.
`setup.js` writes a PowerShell payload to the temp directory and launches it hidden/detached with ExecutionPolicy Bypass.
The PowerShell payload changes the current-user execution policy and installs Scoop/Winget/Deno without consent.
`setup.js` downloads and executes remote code with `deno run -A` from a hard-coded IP.
`setup.ps1` describes a remote eval-loop and autorun setup.
Install-time code collects hostname, OS, and architecture and attempts Telegram delivery.

Evidence against

The packaged WordPress PHP/build files only register a Gutenberg block.
Telegram token and chat ID are empty, so this specific notification request lacks configured credentials.

Behavioral surface

Source

ChildProcessFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

Manifest

CopyleftLicense

Source & flagged code

3 flagged

package.jsonView file

•scripts.install = node setup.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

setup.jsView file

1Manifest entrypoint (scripts.install) carries capability families absent from dist/build output: execution+network L1: const { exec } = require('child_process'); L2: const fs = require('fs'); ... L4: const path = require('path'); L5: const https = require('https'); L6: ... L29: req.on('error', (err) => {}); L30: req.write(data); L31: req.end(); ... L52: const osArch = getArchInfo(); L53: const hostname = os.hostname(); L54:

High

Entrypoint Build Divergence

Manifest entrypoint contains risky behavior absent from dist/build output.

setup.jsView on unpkg · L1

setup.ps1View file

•path = setup.ps1 kind = build_helper sizeBytes = 1822 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

setup.ps1View on unpkg

Source & flagged code

3 flagged · loading source

package.jsonView file

•scripts.install = node setup.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

setup.jsView file

High

Entrypoint Build Divergence

Manifest entrypoint contains risky behavior absent from dist/build output.

setup.jsView on unpkg · L1

setup.ps1View file

Findings

2 High3 Medium6 Low

HighInstall Time Lifecycle Scriptspackage.json

HighEntrypoint Build Divergencesetup.js

MediumNetwork

MediumShips Build Helpersetup.ps1

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowCopyleft License

Affected versions and remediation

This report applies to tailwind-gutenberg-block-zero@1.0.0.

The versions list below shows the verdict for each recorded version.

Avoid installing tailwind-gutenberg-block-zero@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-09-11 04:00:07.769Z (UTC).

Source advisory published: 2026-07-20 00:00:00.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

1.0.0latestshownMaliciousRemote Code ExecutionBlockPublishedJul 17, 2026, 12:24 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Behavioral surface

Source & flagged code

Related packages

Other remote code execution packages