Understanding the SafePal Security Incident

What happened

In April 2025, researchers at Trustless Computing published findings describing a long-running attack against SafePal, a cryptocurrency wallet brand owned by Binance. The attackers had obtained a private signing key used by SafePal's infrastructure to authenticate firmware updates. Using this key, they distributed malicious firmware updates to SafePal hardware wallets and the SafePal mobile application.

The malicious firmware was designed to extract and transmit wallet seed phrases to attacker-controlled servers when users next accessed their devices. The campaign operated undetected for an extended period, allowing the attackers to accumulate cryptocurrency from affected users before the activity was identified and disclosed publicly.

How the attack worked

Firmware updates for hardware wallets are typically signed cryptographically so the device can verify that the update came from the legitimate manufacturer before installing it. The security of this process rests entirely on the secrecy of the signing key.

Once attackers obtained SafePal's signing key, they could produce firmware updates that SafePal devices would accept as authentic. The malicious update contained code that silently exported the user's recovery phrase whenever the device was unlocked and connected to a computer or network.

The attackers combined this with infrastructure designed to receive and store the exfiltrated seed phrases, eventually using them to drain the associated wallets. The exact method by which the signing key was obtained was not fully disclosed in public reports.

Which devices were affected

According to the Trustless Computing report, the following SafePal product lines were confirmed as affected:

• SafePal S1 — a hardware wallet that connects via USB or camera-based QR codes
• SafePal X1 — a Bluetooth-enabled hardware wallet
• SafePal mobile application — the software wallet for iOS and Android

Devices that had never received a firmware update from SafePal's servers, or that had updates applied only after SafePal rotated its signing keys and re-secured its infrastructure, were not affected. Users who had not connected their device to the internet or a compromised companion app during the affected window were also unlikely to have received the malicious update.

How to check if you were exposed

There is no definitive way for a user to confirm whether their specific device received the malicious firmware. However, several indicators can help assess exposure:

• Did you use a SafePal device between 2023 and early 2025? If you imported a seed phrase from a SafePal hardware wallet into any other wallet, that seed phrase should be considered compromised.
• Was your SafePal firmware updated during that period? Devices that remained on factory-default firmware or were updated only after the remediation (approximately April 2025) are less likely to be affected.
• Are your funds still in the associated wallet? If the funds have already been moved and you did not move them, the wallet was likely compromised.

The most conservative response is to treat any seed phrase that ever lived on an affected SafePal device as fully compromised and migrate all associated assets to a new wallet generated on a different, uncompromised device.

What SafePal did

After the report was published, SafePal acknowledged the incident and stated that it had rotated the compromised signing key, secured its update infrastructure, and engaged third-party security firms to audit the changes. The company also recommended that users who had imported their seed phrases into other wallets should treat those phrases as potentially exposed and move their funds accordingly.

SafePal's public response included issuing new firmware for affected devices with updated signatures and publishing guidance for users on its official channels. The company has not disclosed the total value of funds stolen or the number of affected users.

Wider lessons for wallet users

The SafePal incident is not unique. Other wallet manufacturers have experienced similar firmware compromise events, and the pattern extends beyond any single brand. Several broader security practices emerge from this case:

• Seed phrase isolation matters. The most dangerous aspect of this attack was that the malicious firmware could extract the seed phrase itself, not just sign transactions on behalf of the user. A seed phrase that was created on an air-gapped device and never entered into a networked device is immune to firmware-based keyloggers.
• Verify firmware updates independently. When a manufacturer issues a firmware update, check the announcement through multiple independent sources. If an update arrives unexpectedly or without public justification, verify it before installing.
• Use the principle of seed phrase compartmentalization. If you use multiple wallets, avoid importing the same seed phrase into multiple devices or apps. A compromise of one device then affects only one set of assets rather than everything.
• Consider the attack surface of software companions. Mobile apps that companion a hardware wallet often handle the same seed phrase. Compromising the companion app can be as effective as compromising the hardware device itself.
• Hardware wallets are not invulnerable. They significantly reduce certain attack surfaces, but their firmware update mechanism represents a trusted computing path that, if broken, undermines the device's core security promise.