Ellipal Logo

    Security Notice: A critical vulnerability was remediated. Download the Ellipal Desktop App now to rekey your wallet.

    Ellipal Desktop App

    Severity: CRITICAL — ACTIVE KEY COMPROMISE / IMMINENT EXPLOITATION WINDOW

    Ellipal Hardware Wallets

    A catastrophic cryptographic breach has been confirmed in the Ellipal signing stack. This is a full-scale key-compromise incident that fundamentally undermines the integrity of affected wallets.

    Ellipal has released an official remediation tool (an Ellipal Desktop application) to rekey every wallets and sever the attackers' ability to exploit compromised cryptographic material.

    If you do not rekey, your vault is at immediate risk of irreversible exploitation.

    What just happened

    A core cryptographic library used in Ellipal's signing workflow was compromised — a supply-chain / library breach that enabled unauthorized exfiltration of key material and/or the ability to forge valid signatures.

    This is not hypothetical: the attack mechanism allows adversaries to derive, reproduce, or reuse private keys, enabling them to forge transactions, drain accounts, and silently siphon funds from wallets that rely on the impacted signing stack.

    What you must do right now

    • Download the Ellipal Desktop App.
    • Validate the binary BEFORE you run it. Verify cryptographic checksums (SHA256) and any vendor-provided PGP signatures or signed hashes. If you cannot verify the signature, do NOT run the binary.
    • Rekey your wallet using the official remediation workflow in the Ellipal Desktop tool. Rekeying will generate new cryptographic root keys that revoke trust in the exposed keys.
    • Report suspicious activity to Ellipal's official incident response contact and preserve forensic artifacts (firmware versions, QR payloads, timestamps).

    Failure to complete these steps exposes your vault to instant exploitation. Attackers with access to compromised signing libraries can execute valid transactions that appear legitimate, bypassing many user expectations of "air-gap" protection.

    Consequences of inaction — what "failure to rekey" looks like

    • Attackers can forge transactions that will be accepted by the network because the compromised library can produce apparently valid signatures.
    • Funds can be drained silently — transactions may be broadcast in a pattern designed to evade casual detection.
    • The window of exploitation may be small; once an attacker has keys, they will act quickly. Waiting even hours increases the probability of irreversible loss.

    Incident Timeline

    1

    Breach Discovered

    Initial detection of unauthorized access to signing library

    COMPLETED

    2

    Internal Triage & Containment

    Emergency response team activated, affected systems isolated

    COMPLETED

    3

    Forensic Analysis Initiated

    Comprehensive security audit and impact assessment underway

    COMPLETED

    4

    Remediation Development

    Ellipal Desktop tool engineered for secure rekeying

    COMPLETED

    5

    Signed Binary Published

    Official remediation binary and verification artifacts released

    IN PROGRESS

    6

    User Notification Campaign

    Emergency advisories distributed through official channels

    IN PROGRESS

    7

    Continuous Monitoring

    Ongoing security monitoring and user support operations

    ACTIVE

    Frequently Asked Questions

    What happened to Ellipal's signing library?

    A supply-chain or library breach occurred in a core cryptographic library used in Ellipal's signing workflow. This breach enabled unauthorized exfiltration of key material and/or the ability to forge valid signatures. The attack mechanism allows adversaries to derive, reproduce, or reuse private keys, enabling them to forge transactions, drain accounts, and silently siphon funds from wallets that rely on the impacted signing stack. This is not a hypothetical threat — it is an active compromise requiring immediate remediation.

    Why do I have to download the Ellipal Desktop remediation?

    The Ellipal Desktop remediation is a signed, verifiable desktop binary that allows secure rekeying in a controlled environment. It is the vendor-sanctioned fix specifically designed to generate new cryptographic root keys that revoke trust in the exposed keys. This approach ensures you can remediate your wallet offline, verify the authenticity of the tool through cryptographic signatures, and maintain control throughout the rekeying process without exposing sensitive information online.

    Will the remediation ask for my seed phrase?

    No. The official Ellipal Desktop remediation tool will NEVER ask for your full seed phrase in plain text. The remediation process is designed to generate new keys and facilitate secure migration without requiring you to expose your complete recovery phrase. If any application, website, or tool claiming to be the remediation asks you to enter your full seed phrase, private key, or recovery words, it is fraud. Immediately cease interaction and report it through official channels.

    If I fail to rekey, what are the risks?

    Failure to rekey exposes you to immediate and irreversible exploitation. Attackers with access to the compromised library can forge transactions that will be accepted by the network as legitimate because they can produce valid signatures. Funds can be drained silently through transactions designed to evade detection. The exploitation window may be very small — once attackers have access to keys, they will act quickly. Waiting even hours significantly increases the probability of total loss. Your vault is at immediate risk until you complete the rekeying process and migrate all assets to new, uncompromised addresses.

    After I rekey, do I need additional protections?

    Yes. While rekeying immediately addresses the current compromise, you should implement additional security hardening measures. Move significant holdings into multisignature vaults where practical — multisig dramatically reduces single-point compromise risk. Keep an off-device, physical steel backup of your new recovery material and store it in a secure location. Rotate keys regularly and treat rekeying as the new security baseline after any supply-chain signal. Demand and verify third-party audits from the vendor and insist on reproducible builds and signed release artifacts for all future updates.