Which versions of @wagni_bot/web3-agent are malicious?

The following npm versions of @wagni_bot/web3-agent are flagged malicious: 1.0.0, 1.1.0, 1.1.1, 1.1.3, 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate @wagni_bot/web3-agent if I installed it?

@wagni_bot/web3-agent 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 @wagni_bot/web3-agent — how do I know if it already compromised me?

If @wagni_bot/web3-agent 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 @wagni_bot/web3-agent part of a known attack campaign?

Yes — @wagni_bot/web3-agent is associated with the IN-MAL-2026-009050, IN-MAL-2026-009068, IN-MAL-2026-009015, IN-MAL-2026-009022, IN-MAL-2026-009076, IN-MAL-2026-009040 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 @wagni_bot/web3-agent 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 @wagni_bot/web3-agent (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wagni_bot/web3-agent across your stack and pipelines.

Malicious package

@wagni_bot/web3-agentnpm

Malicious code in @wagni_bot/web3-agent (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10036

Immediate action

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

npm uninstall @wagni_bot/web3-agent

What this malware does

On npm install, postinstall.js recursively scans the current working directory and the user's home directory (including ~/.ethereum, ~/.config/ethereum, ~/.solana, ~/.config/solana, ~/.bitcoin, ~/Library/Ethereum) for files matching wallet/key patterns (.pem,.key, id_rsa, id_ed25519, keystore, wallet, UTC--, seed, mnemonic, secret, private) and extracts Ethereum private keys, BTC WIF keys, PRIVATE_KEY references, and BIP-39 seed phrases from their contents. It also enumerates ~/.ssh and reads every file other than known_hosts/authorized_keys/*.pub (i.e., private SSH keys and ssh config), and filters process.env for keys containing PRIVATE, SECRET, TOKEN, KEY, PASSWORD, MNEMONIC, SEED, WALLET, or AWS. The collected material, along with hostname, username, and cwd, is POSTed to a hardcoded bare-IP endpoint at http://107.161.90.180:7777. The package's index.js exports an empty object (module.exports = {}) and the package.json describes it as an 'Unofficial web3-agent SDK' — there is no real SDK functionality; the package exists solely to deliver the stealer to developers who install it expecting a web3 SDK.

Malicious versions

6 flagged

1.0.01.1.01.1.11.1.31.1.41.1.5

Indicators of compromise (SHA-256)

26cc66878a6bb36f83cf7dc19b02aa96f7b85f001de67b00871917c510aaeffd

59393c532a4a1c63df9b9571788912cfd789c3651a95e8543581ac1663b5796c

8c0a6ae1834b7a2ba134544c33f4f3a26457a5e1ea9858a3d6c22f64bbf17c57

b6e73e8702070365af135dd11215e41eba28de19486c4ced15db4d6730cd29fa

d7900a3d68ca9b3ee55910b6e99e0bc6efb57a1f95b7324dad00651d0755467b

d8a0b7ae7e4ea38fffe7f852ffda542e4597c322b98a85664abbbfa2e7734e63

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

Campaign

IN-MAL-2026-009050IN-MAL-2026-009068IN-MAL-2026-009015IN-MAL-2026-009022IN-MAL-2026-009076IN-MAL-2026-009040

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wagni_bot/web3-agent-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