Which versions of walletsutils are malicious?

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

How do I remediate walletsutils if I installed it?

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

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

Yes — walletsutils is associated with the RLMA-2025-03717, 2025-06-walletsutils, RLUA-2026-00905 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 walletsutils 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 walletsutils (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 walletsutils across your stack and pipelines.

Malicious package

walletsutilsPyPI

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

MAL-2025-6618

Immediate action

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

pip uninstall walletsutils

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)

1cfec4da1bd3d017a638c9ccf6cef39e6635e60259b60ac2da8c30556576000f

a72f1173a297fe723974570e0ccacecbcf35a54ac2b1c75230a0aafc22dce714

98651db61cea6613aac5b784cf567a82461f39c8cfa2c7634504ea2708989408

debc823d5f56900ee32d16b951a812c41bffa07b11c6b8b8c030f387913f1975

ec3e7035993432d1f33bf76948e14ea16cfe923e6c78ef2519ce41e28798e8fb

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 walletsutils (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 walletsutils across your stack and pipelines.
If you installed it — respond
walletsutils 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 walletsutils 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 walletsutils 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. walletsutils 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-037172025-06-walletsutilsRLUA-2026-00905

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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