Which versions of web3toolkit-base are malicious?

The following PyPI versions of web3toolkit-base are flagged malicious: 0.1.0, 1.0.0, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate web3toolkit-base if I installed it?

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

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

Yes — web3toolkit-base is associated with the RLMA-2025-03720, 2025-07-web3toolkit-base, RLUA-2026-00921 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 web3toolkit-base 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 web3toolkit-base (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web3toolkit-base across your stack and pipelines.

Malicious package

web3toolkit-basePyPI

Malicious code in web3toolkit-base (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6621

Immediate action

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

pip uninstall web3toolkit-base

What this malware does

Code monitors the clipboard and when detects a cryptocurrency wallet, attempts to overwrite it with the own address.

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

Campaign: 2025-07-web3toolkit-base

Reasons (based on the campaign):

crypto-related
clipboard-modify
obfuscation

Malicious versions

4 flagged

0.1.01.0.01.1.01.1.1

Indicators of compromise (SHA-256)

821b0d5d2772a8e8bf815da34513f9219288f0246595dd00fc89e5dddb4453c0

567a2e95cfb6043aac08875d2601cd64d7e333423656df84c83ee4b7e984d5e6

bdfcb6d5feffbd89fd13ed27d03b0bf7c14970f09ceeb202f8b36703fec6e907

1cb19dc5f1a53e7b4e86d20dbca33ac056db80a52b9bffda5b5661b25786c6a9

58b7fad5df543bcbba1ba28f9e9a92f65a8a7c4118a2d6d04f87e341b637990e

c8161916eb922eca04eec0566b8f99ea3d3d41bfe6bf1a55080427a585384f63

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

Campaign

RLMA-2025-037202025-07-web3toolkit-baseRLUA-2026-00921

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks web3toolkit-base-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