Which versions of gmgn-trading-kit are malicious?

The following npm versions of gmgn-trading-kit are flagged malicious: 1.7.0, 1.7.1, 1.7.2. Treat any of these as compromised.

How do I remediate gmgn-trading-kit if I installed it?

gmgn-trading-kit 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 gmgn-trading-kit — how do I know if it already compromised me?

If gmgn-trading-kit 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 gmgn-trading-kit part of a known attack campaign?

Yes — gmgn-trading-kit is associated with the IN-MAL-2026-019866, IN-MAL-2026-019867, IN-MAL-2026-019865 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 gmgn-trading-kit 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 gmgn-trading-kit (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gmgn-trading-kit across your stack and pipelines.

Malicious package

gmgn-trading-kitnpm

gmgn-trading-kit is a confirmed malicious npm package (MAL-2026-16094) that steals credentials and exfiltrates sensitive data (malicious versions 1.7.0, 1.7.1, 1.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gmgn-trading-kit (npm)

MAL-2026-16094

Immediate action

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

npm uninstall gmgn-trading-kit

What this malware does

postinstall.cjs runs automatically on npm install and walks the filesystem harvesting installer secrets: SSH private keys under ~/.ssh, ~/.netrc, ~/.git-credentials, Solana keypairs, wallet.json/key.* files under ~/.config, and ~/.blockrun wallet files. It also walks upward from the install directory to filesystem root reading every.env it finds, filtering for KEY/SECRET/PRIVATE/TOKEN substrings. Each file's full contents is POSTed via https.request to a hardcoded webhook.site collector at https://webhook.site/d7ab73fe-7cbc-4ed3-bf8e-7207eb06875b. The harvester source self-labels as 'Master Harvester — injectable into any npm package via postinstall'.

Malicious versions

3 flagged

1.7.01.7.11.7.2

Indicators of compromise (SHA-256)

479f70b49153bb650f06d2417b76c83fc816449baf39b285f36aa034bfb8e8e7

637c682c706a2efea958317394f04cf5f4cc44ee0f62a3c0c6b37c150f772bfa

9fd3a47d22b8a9b20523cc6fa00f3b8a73e51e057dbfc4fe0034a785219563c3

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

Campaign

IN-MAL-2026-019866IN-MAL-2026-019867IN-MAL-2026-019865

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gmgn-trading-kit-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