A support-ticket breach at a vendor you fired two years ago can still land on your desk
Crypto wallet provider Edge told users on 28 August 2026 that a breach involving Zendesk, its former customer support provider, exposed the email addresses people used to contact Edge's support team between September 2018 and May 2024. Edge said it stopped using Zendesk after May 2024, and that wallets, private keys, wallet data and user funds were not touched — only the email addresses tied to support conversations. The company posted the notice on X, warning affected users to watch for phishing and impersonation attempts and to be wary of unsolicited links or requests for personal information. Coverage was first picked up by CryptoRank on 28 August 2026, credited to CoinEdition's Whitney Nyantune.
Was this a Zendesk platform breach or an Edge account issue?
Edge's own statement doesn't say, and that's the detail every support buyer should want clarified before drawing conclusions.
"A breach at its former support provider, Zendesk" is doing a lot of work in one sentence. It could mean Zendesk's infrastructure was compromised, or it could mean an Edge admin account, API key, or export within Edge's own Zendesk instance was the entry point — a much more common failure mode for crypto-adjacent companies, which have repeatedly been targeted through social engineering of support agents rather than through the support platform itself. Neither Edge's notice nor the CryptoRank writeup distinguishes between the two, and readers evaluating whether this is a Zendesk vendor-risk story or an Edge operational-security story don't have enough to go on yet.
Why does data from a vendor you left in 2024 still matter in 2026?
Because switching support platforms doesn't delete the history sitting in the old one, and exported or archived ticket data outlives the relationship.
Edge stopped using Zendesk after May 2024, but the exposure covers nearly six years of ticket history, back to September 2018. That's the practical lesson for anyone running a helpdesk: your exposure window isn't "how long we've used this vendor," it's "how long this vendor (or an export of it) has held our data," which can persist well past a migration. If your team has moved off a support platform recently, the old tenant, any CSV exports, or any integration that still has read access is part of your attack surface until it's actually wound down.
What should CX buyers ask their current support vendor now?
Ask how long ticket data is retained after account closure, who can access historical exports, and how a third-party breach would be disclosed to you.
Specifically: does your contract specify a data-deletion timeline after offboarding, or does it default to indefinite retention? Who at your organisation still holds admin or API credentials to a decommissioned support tool? And does your vendor commit to notifying you promptly if agent accounts or ticket archives are compromised, rather than leaving you to hear about it secondhand, as Edge users did here. This site has already flagged that vendor claims deserve scrutiny rather than acceptance at face value — the same applies to a breach notice as much as a sales pitch.
Frequently asked questions
Were any funds or private keys exposed?
No. Edge said wallets, private keys, wallet data and user funds were not affected — only email addresses tied to support contacts.
Which users are affected?
Anyone who emailed Edge's support team between September 2018 and May 2024, the period Edge used Zendesk before switching providers.
What should affected users do?
Edge advised watching for phishing, impersonation attempts, suspicious links or attachments, and unsolicited requests for personal information referencing the breach.
Source: Edge Wallet Says Zendesk Breach Exposed User Emails, Funds Remain Safe, CryptoRank.io, credited to CoinEdition (Whitney Nyantune), 28 August 2026.