Which versions of babel-plugin-blocks are malicious?

Every published version of babel-plugin-blocks on npm is considered malicious. Remove the package entirely.

How do I remediate babel-plugin-blocks if I installed it?

babel-plugin-blocks 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 babel-plugin-blocks — how do I know if it already compromised me?

If babel-plugin-blocks 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 babel-plugin-blocks part of a known attack campaign?

Yes — babel-plugin-blocks is associated with the GHSA-9h8x-6qpc-9v5g 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 babel-plugin-blocks 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 babel-plugin-blocks (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-plugin-blocks across your stack and pipelines.

Malicious package

babel-plugin-blocksnpm

Malicious code in babel-plugin-blocks (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2631

Immediate action

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

npm uninstall babel-plugin-blocks

What this malware does

Malicious package due to data exfiltration via test, preinstall, and preupdate scripts in package.json using wget to send data to webhook.site.

The package babel-plugin-blocks was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

a015c55cc9f30e0285066d4e18fa6a2d5293e56556b302339803201491f8da1e

679960b444e4781d7276df8692808a4bc4507d29aefe943ffe4d3dfb35dcc141

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 babel-plugin-blocks (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging babel-plugin-blocks across your stack and pipelines.
If you installed it — respond
babel-plugin-blocks 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 babel-plugin-blocks 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 babel-plugin-blocks 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. babel-plugin-blocks on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9h8x-6qpc-9v5g

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks babel-plugin-blocks-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