Which versions of walletweb3 are malicious?

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

How do I remediate walletweb3 if I installed it?

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

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

Yes — walletweb3 is associated with the RLMA-2025-02618, 2025-04-alchemyrpcs, RLUA-2026-00909 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 walletweb3 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 walletweb3 (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 walletweb3 across your stack and pipelines.

Malicious package

walletweb3PyPI

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

MAL-2025-4260

Immediate action

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

pip uninstall walletweb3

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)

4c65d21d4977f4a151805ab225fa2b8beff2145c92914d70faa6e9d0044fe518

cc21c044506edaa373c58948c994943cb7c313d8023b1778309409051b9d2bed

03c7d45b1b392aae3891836f4e5083004be7ac61c0001ee649b834fefceb638d

43fcf1c77be5210384e5fd2b94bdb1c9fd9f0a6a9e92af53fb4db75dec36219b

0ec52221e213eac640a5bfa7376144ead1903faa909a1f4d51057af81700d89a

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 walletweb3 (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 walletweb3 across your stack and pipelines.
If you installed it — respond
walletweb3 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 walletweb3 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 walletweb3 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. walletweb3 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-026182025-04-alchemyrpcsRLUA-2026-00909

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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