Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

gate-evm-tools-testnpm

Malicious code in gate-evm-tools-test (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190844
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall gate-evm-tools-test

What this malware does

The package gate-evm-tools-test 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

4 flagged
1.0.51.0.61.0.71.0.8

Indicators of compromise (SHA-256)

ff4f4b0be20489896990e369ba464373595724d046d2c6a6cf491b35031a29af
f11f5364b5246431e888b7293099cd8833dbcdd463cc7ce7d1aeabdc066faa5a
5ca2f5cea8d3d237646ed8c511d5710ff134fa307491842547d5c11a05c7de3e
2f8256094bf975941c01b8de23d3f7c032804eb0016b472d6a9dfd645b9c28b8

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gate-evm-tools-test (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gate-evm-tools-test across your stack and pipelines.

  2. If you installed it — respond

    gate-evm-tools-test 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.

  3. Did it already run?

    If gate-evm-tools-test 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.

  4. How O3 protects you

    O3 blocks gate-evm-tools-test 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. gate-evm-tools-test on npm has been identified as a malicious package (versions 1.0.5, 1.0.6, 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r39v-gqh6-q9mr

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gate-evm-tools-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

gate-evm-tools-test (npm) malicious package — MAL-2025-190844 | O3 Security