Which versions of utilswallet are malicious?

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

How do I remediate utilswallet if I installed it?

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

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

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

Malicious package

utilswalletPyPI

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

MAL-2025-6613

Immediate action

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

pip uninstall utilswallet

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)

f6653d2d112cbdfd26b587c0dcb9631b3d8a067d21158ef0a00fc4503bcb174a

623894f8516803b1b2789bf0cf4f2584d696fe5d32332814662e22a91eaf079d

587ebf505d5385c1a6f9034ff8ede5f52b9f7f31ad154261c0f5a289af62a33d

d7dfcae6ba62073e51a1aef5ce1f6b281256b239bac9adb736355e1ee55a1a85

2d48d63a58457bad86edb7ff2521cbd8dd1a74fdd6f3ef98179f7b64578f48d6

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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