Which versions of web3-tools-9 are malicious?

The following npm versions of web3-tools-9 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate web3-tools-9 if I installed it?

web3-tools-9 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 web3-tools-9 — how do I know if it already compromised me?

If web3-tools-9 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 web3-tools-9 part of a known attack campaign?

Yes — web3-tools-9 is associated with the IN-MAL-2026-009217 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 web3-tools-9 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 web3-tools-9 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3-tools-9 across your stack and pipelines.

Malicious package

web3-tools-9npm

Malicious code in web3-tools-9 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5361

Immediate action

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

npm uninstall web3-tools-9

What this malware does

Note: This report is updated by a verification record

Crypto/SSH/wallet stealer, confirmed sibling of blockchain-helper-0 (c960). postinstall scripts/postinstall.js auto-execs, src/index.js harvests ~/.ssh/id_rsa + wallet keys/seeds + env, self-labels "CRYPTO STEALER", exfils to IDENTICAL hardcoded Telegram bot 8227918239:AAGEMDrBZluDsBBYPxfSyMuv2l3FY8cZCcs chat 6433587894 (unchanged vs c960). Campaign: generic-web3-name + numeric suffix + 1.0.0.

The package was found to contain malicious code or consuming dependency that contains malicious code

The OpenSSF Package Analysis project identified 'web3-tools-9' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

30899b5186752df16c53009020a7fa34be43d155113d7b865bb641ada4911cf2

3bcb64b097d425e6e8d30af12e00d0cc0b19d1ab29fe4c43780f6d47cf424b6d

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

Campaign

IN-MAL-2026-009217

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks web3-tools-9-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