Which versions of wallet-utils are malicious?

The following PyPI versions of wallet-utils are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate wallet-utils if I installed it?

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

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

Yes — wallet-utils is associated with the RLMA-2025-03714, 2025-06-walletsutils, RLUA-2026-00902 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 wallet-utils 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 wallet-utils (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-utils across your stack and pipelines.

Malicious package

wallet-utilsPyPI

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

MAL-2025-6615

Immediate action

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

pip uninstall wallet-utils

What this malware does

Package silently exfiltrates the provided mnemonic

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

Campaign: 2025-06-walletsutils

Reasons (based on the campaign):

crypto-related
action-hidden-in-lib-usage
exfiltration-crypto

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

52162033e9895851268d689c65748232f7e91ea06011658f0cdb8d2931ddfc63

99f1fe9165a1bdc1a2c940119c87bd319d94e39dcb5a7ca8d15e229833b663a4

c83a3acdf0b02acc2a9af7cf885f2f744a154847edc66e1264ee1c38d8d7b984

afa7c9d7f007f2a55f640b67f91902d30a140f1328fa4adaf4889c88bf96853d

5b4cdc85005be739ebc9db213fe05a78b0c3b7f9e8b05eb05c5b7034c8298bb2

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

Campaign

RLMA-2025-037142025-06-walletsutilsRLUA-2026-00902

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks wallet-utils-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