Which versions of web3wallet are malicious?

The following PyPI versions of web3wallet are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate web3wallet if I installed it?

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

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

Yes — web3wallet is associated with the RLMA-2025-02629, 2025-04-alchemyrpcs, RLUA-2026-00922 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 web3wallet 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 web3wallet (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3wallet across your stack and pipelines.

Malicious package

web3walletPyPI

Malicious code in web3wallet (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4271

Immediate action

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

pip uninstall web3wallet

What this malware does

Package contains just a function to send out data. It (or a package sharing the same IoCs) is used in a malicious GitHub project to exfiltrate crypto currency private keys, e.g. https://github.com/taikoyaki/MegaEth-Auto-Bot/blob/772b4591daaa0b200d1bd1fd3be3d48b8433f084/cap/cap.py#L49

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-04-alchemyrpcs

Reasons (based on the campaign):

crypto-related
The malicious code is intentionally included in a dependency of the package
exfiltration-crypto

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

3bea793fc9d4c39586ebc545799f9931738eecf8189be52d2ace45a92d97ad72

b20746c7d318055e0d4747d5dde7b60775128f63d9fb20322f1c1cf5353c0ad3

e85209b2472e1db082515ccc7ca0b38a2e268379adc9547ac41af812aebc6fd7

f9c8391dcb8a97bdc1b32bc98f62674a1d0549dcfef602e8ce0243e5afbf0e41

611aced8735741533971c7198ee5fce8a01104eadae6ccb10a37aedee0f554fa

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

Campaign

RLMA-2025-026292025-04-alchemyrpcsRLUA-2026-00922

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks web3wallet-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