Which versions of walletsdk are malicious?

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

How do I remediate walletsdk if I installed it?

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

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

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

Malicious package

walletsdkPyPI

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

MAL-2025-6617

Immediate action

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

pip uninstall walletsdk

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)

d10fc0bf9e9c3a904d73d22d614d326cce7f55f04e90f5b3fed388e8a06940c1

dfbd806c382dace58865774cf3b83cd879c21fba9788914b4981b1000611460d

24b8f8046f66b9996b1f2169f1034b1c35f0760e09d4e91e712d0b3a36a88d6e

051954efd0b11759a73af0bc8b3d90fc3b24c6ff3cddd61a362477e5812a677c

827fe7d13053d07284d71c6666231d573632c33f73a3e412afb2296a1d718013

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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