Which versions of gatsby-plugin-antd are malicious?

The following npm versions of gatsby-plugin-antd are flagged malicious: 2.2.1. Treat any of these as compromised.

How do I remediate gatsby-plugin-antd if I installed it?

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

If gatsby-plugin-antd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is gatsby-plugin-antd part of a known attack campaign?

Yes — gatsby-plugin-antd is associated with the GHSA-cvhw-3383-wcw3 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 gatsby-plugin-antd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gatsby-plugin-antd (version 2.2.1).

Malicious package

gatsby-plugin-antdnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

gatsby-plugin-antd is a confirmed malicious npm package (MAL-2025-191396) that steals credentials and exfiltrates sensitive data (malicious version 2.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gatsby-plugin-antd (npm)

MAL-2025-191396

Immediate action

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

npm uninstall gatsby-plugin-antd

What this malware does

The package gatsby-plugin-antd 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

2.2.1

Indicators of compromise (SHA-256)

0bc7645ab024806cb25cf37f5b0f778aaeaf3b627fc1f9b6075285553818a07b

595478487dbe48a9909073a9f2b373790b1d70fd38c5fd3055706f9eb6a1a969

1db5c29950300909f2a9571826a482e10a6ce45dae9529f28ad87ddc2b98119b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gatsby-plugin-antd (version 2.2.1).
If you installed it — respond
gatsby-plugin-antd 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 gatsby-plugin-antd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-cvhw-3383-wcw3

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gatsby-plugin-antd-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