Hims & Hers support-ticket breach: Zendesk reached through a hijacked Okta SSO account

Hims & Hers says attackers read support tickets on its help desk on 4-7 February 2026. Reports tie it to a ShinyHunters Okta SSO campaign. What to fix.

TechLogHub Engineering Team
April 3, 2026
3 min read
0 views

Share Article

Hims & Hers Warns of Data Breach After Zendesk Support Ticket Leak

Telehealth company Hims & Hers has disclosed that attackers accessed customer support tickets on its third-party customer service platform between 4 and 7 February 2026. Reporting links the breach to a ShinyHunters campaign that used compromised Okta single sign-on accounts to reach Zendesk instances. Support tickets are an easy-to-forget store of customer data, and SSO turns one stolen login into access to every connected app.

What happened

According to Hims & Hers' notification, filed with California regulators, the company detected suspicious activity on its third-party customer service platform on 5 February 2026 and secured it. The investigation found that support tickets were accessed or taken without authorisation from 4 to 7 February. On 3 March the company confirmed that some tickets contained personal information. The company called it "a sophisticated social engineering attack".

The exposed data may include names, contact details and other information customers put in support requests. The company says medical records and communications with healthcare providers were not affected. It has not said how many people were affected and is offering 12 months of free credit monitoring and identity protection.

BleepingComputer's sources say the ShinyHunters extortion group was behind the attack, using a compromised Okta SSO account to reach the company's Zendesk instance and steal "millions of support tickets". Hims & Hers has not confirmed the attribution. The same reporting describes a wider campaign in which attackers took over Okta SSO accounts to reach cloud and SaaS platforms. Earlier Zendesk-related breaches it cites include DIY retailer ManoMano (February 2026) and Crunchyroll (March 2026). Security coverage of the campaign describes attackers posing as IT support on the phone and steering employees to fake login pages to collect passwords and MFA codes.

Who is affected

  • Hims & Hers customers who contacted support around or before the incident. Their names, contact details and whatever they wrote in tickets may be exposed. Expect targeted phishing that refers to real support conversations.
  • Any company using SSO to reach a help desk (Zendesk, Freshdesk, Intercom, Salesforce Service Cloud) where agents can search or export large numbers of tickets.

What it means for developers and engineering teams

Two design facts make this kind of breach effective. First, support tickets collect sensitive data by accident. Customers paste order numbers, addresses, screenshots and sometimes health or payment details, and tickets are kept for years by default. Second, SSO centralises access. That is good for offboarding and MFA, but an attacker who gets one Okta session gets every app tile behind it, including the help desk, which usually has bulk search and export.

The attack doesn't exploit a software bug. It uses a real user's session from the attacker's own machine. Detection has to look at behaviour: a new device and location for that user, followed by API or export activity far above that agent's normal volume.

For engineering teams that own support tooling and integrations, the questions are practical. Which API tokens and OAuth apps can read all tickets? Does anything redact card numbers or health data on ingest? How long do closed tickets live? Can one agent export everything?

What to do now

  1. Use phishing-resistant MFA for SSO. Enforce FIDO2/WebAuthn (or Okta FastPass with device binding) for all workforce users, starting with support agents and admins. OTP and push codes can be phished over the phone.
  2. Harden help desk identity checks. Your IT support should never ask for MFA codes, and staff should know that. Verify any caller asking for MFA resets through a callback.
  3. Bind and limit sessions. Use Okta policies that require managed devices for sensitive apps, shorten session lifetimes and re-authenticate for admin and export actions.
  4. Audit help desk access. Review Zendesk API tokens and OAuth clients, remove unused ones, and limit bulk export to a small admin group.
  5. Reduce what tickets keep. Turn on redaction for card numbers and other sensitive fields, and set deletion schedules for closed tickets in line with your retention policy.
  6. Alert on bulk reads. Stream help desk audit logs and API usage to your SIEM and alert on spikes in ticket views, searches or exports per user.

Related on TechLogHub

Sources

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.

Hims & Hers Zendesk Breach via Okta SSO: Lessons | Hims Hers Warns Of Data Breach After Zendesk Support Ticket Leak