Reports agree SafePal suffered a data breach affecting roughly 40,000 customers, but disagree on whether SafePal issued a formal disclosure with a specific figure.
What all sources agree on
- SafePal experienced a data breach affecting customer order data for roughly 40,000 users.
- No seed phrases, private keys, or crypto funds were compromised.
- Exposed data included names, addresses, and contact/order details.
- The breach has been linked to concerns about phishing and impersonation risks for affected users.
Where the reports disagree
1Whether SafePal issued a formal breach disclosure naming a specific number of affected users
As of the time of reporting, SafePal had not issued a formal breach disclosure naming a specific number of affected users. The figure of approximately 40,000 impacted customers emerged from external estimates rather than official company communications.
SafePal disclosed a security breach that exposed the names, physical addresses and contact details of 39,798 customers who placed orders between March 2, 2025, and April 11, 2026.
SafePal has disclosed a significant security incident affecting nearly 40,000 customers due to a flaw in its order-tracking plugin.
What would settle it: SafePal's official public statement or press release regarding the breach
2Whether SafePal directly notified affected customers
SafePal notified all affected customers by email from security@safepal.com on Sunday and hired an independent third-party security firm to audit the fix and review its order-processing systems.
As of the time of reporting, SafePal had not issued a formal breach disclosure naming a specific number of affected users.
What would settle it: Copies of SafePal's customer notification emails or a company statement confirming direct outreach
What to make of it
Treat the existence of the breach and the absence of wallet/fund compromise as established; treat the precise customer count (39,798) and whether SafePal made a formal, detailed disclosure as unresolved until SafePal's own statement or filing is checked.
Treat the existence of the breach and the absence of wallet/fund compromise as established; treat the precise customer count (39,798) and whether SafePal made a formal, detailed disclosure as unresolved until SafePal's own statement or filing is checked.