Case Library / Phishing / 0ktapus: the 2022 Okta smishing campaign behind the Twilio breach
Phishing Documented incident

0ktapus: the 2022 Okta smishing campaign behind the Twilio breach

In 2022, 0ktapus texted staff fake IT alerts linking to Okta lookalikes, stealing 9,931 logins and MFA codes. Twilio was breached; Cloudflare's keys held.

Share:

Social Engineering Examples·7 sources

From March to August 2022, a group researchers call 0ktapus sent text messages to employees of companies that use Okta for logins. The texts posed as the company's IT team, warning of an expired password or a schedule change, and linked to a perfect copy of the company's Okta login page. Group-IB found the attackers had collected 9,931 credentials and 5,441 MFA codes across 136 corporate email domains. Twilio, Mailchimp and Klaviyo were breached. Cloudflare was targeted but stopped it. Status: Documented campaign.

Key takeaways

  • One-time codes didn't help. The fake page asked for the code and passed it to the attackers before it expired.
  • Cloudflare had three employees enter their details, and still wasn't breached, because it used hardware security keys.
  • Breaching one supplier opened doors to its customers, including Signal and DigitalOcean.
  • The tools were simple. The success came from texts that looked like routine IT messages.

How the attack worked

Step What happened
Domains The attackers registered lookalike addresses mixing the target's name with words like "okta", "sso", "vpn" or "help". Group-IB found 169
Text Employees got an SMS "from IT": password expired, or schedule changed, with a link
Fake login The link opened an exact copy of the company's Okta page
Live relay Usernames and passwords went straight to the attackers via Telegram, who used them on the real site
MFA code The fake page then asked for the one-time code, which was relayed and used before it expired

SMS was chosen on purpose. Texts feel personal and urgent, and they skip email filters. In some cases the page also pushed the AnyDesk remote-access tool. Cloudflare said its lookalike domain was registered less than 40 minutes before the texts went out. This is smishing combined with credential harvesting.

Tip: IT doesn't text you urgent login links. If one arrives, go to your company's login page the usual way instead.

Who was hit

Company What happened
Twilio Breached; detected 4 August 2022. Its final count was 209 affected customers and 93 Authy accounts
Signal (via Twilio) About 1,900 phone numbers exposed to possible re-registration
Mailchimp Breached; this touched DigitalOcean's transactional email
Klaviyo Breached
Cloudflare Targeted on 20 July 2022; not breached

Group-IB found the operation while investigating a client incident and published it on 25 August 2022. Of the 9,931 credentials, about 3,120 used corporate email addresses. Most targets were US technology, software and cloud firms. No dollar figure for the whole campaign has been published. Later reporting linked the tactics to the wider Scattered Spider ecosystem; Okta tracked related activity as "Scatter Swine".

Why Cloudflare wasn't breached

76 Cloudflare employees received the texts and three entered their credentials. That should have been enough. It wasn't, because Cloudflare used FIDO2 hardware security keys. Those keys check which website is asking before they respond, so they won't work on a fake site. The same attack that broke into companies relying on one-time codes failed against the keys.

What stops it

  • Phishing-resistant MFA, such as hardware keys, instead of SMS or app codes.
  • Know your real login address, and never sign in from a texted link.
  • Block new and lookalike domains with DNS filtering, and watch for registrations using your brand.
  • Block unapproved remote-access tools like AnyDesk.
  • Make reporting easy, and reset passwords and sessions fast when someone does report.

See also the 2020 Twitter hack, which used the same live-relay trick by phone, and account takeover.

Common questions

What was 0ktapus?

A 2022 smishing campaign that sent fake IT texts to employees and harvested Okta logins and MFA codes from more than 130 organisations.

How did 0ktapus beat MFA?

The fake login page asked for the one-time code too, and the attackers used it on the real site within seconds, before it expired.

Which companies were hacked by 0ktapus?

Twilio, Mailchimp and Klaviyo were breached. Signal and DigitalOcean were affected through those suppliers. Cloudflare was targeted but not breached.

Was Okta itself hacked?

No. The attackers faked Okta login pages to steal the credentials of Okta's customers' employees.

Sources
Cite this case

Social Engineering Examples. “0ktapus: the 2022 Okta smishing campaign behind the Twilio breach”. Accessed 3 November 2026. https://socialengineeringexamples.com/0ktapus-okta-phishing-campaign-2022

Attack Chain & Defense
1Reconnaissance and target list-building
What happened

The operation is documented (per Twilio's own incident report and the CISA/FBI advisory AA23-320A on the related Scattered Spider ecosystem) as compiling employee names and personal mobile phone numbers, in some cases including family members, likely drawn from data brokers, prior breach dumps, or OSINT such as LinkedIn and corporate directories, to make bulk SMS lures land convincingly.

The control that would have stopped it

Employee and family personal phone numbers scattered across data brokers and breach dumps are largely outside a company's direct control; the realistic control sits downstream, training staff to distrust unsolicited "IT" texts no matter how the attacker got the number, and watching for bulk lookalike-domain registrations against the brand.

2Infrastructure setup
What happened

Attackers registered lookalike domains pairing the target company's brand with identity-provider keywords such as "okta," "sso," "vpn," "mfa," and "help" through low-friction registrars, and built a phishing kit that cloned the victim's exact Okta/SSO login page, hosted on commodity cloud infrastructure; Group-IB catalogued 169 such domains.

The control that would have stopped it

Monitor domain registrars and certificate-transparency logs for newly registered lookalike domains combining the company brand with SSO-related keywords, and use secure web gateway or DNS filtering that flags or blocks very recently registered domains by default.

3Mass SMS lure delivery
What happened

Attackers sent bulk smishing texts spoofed as internal IT or help desk, using urgency themes like password expiration or a schedule change, and rotated across phone numbers and carriers to stay ahead of blocking.

The control that would have stopped it

Give employees a fast, low-friction way to report suspicious texts to a security team, and train staff that legitimate IT will not send urgent, unsolicited login links by SMS.

4Credential harvesting via cloned login page
What happened

Employees who clicked through landed on the pixel-accurate fake Okta page and entered their username and password, believing it was their real employer SSO portal.

The control that would have stopped it

Verify the exact SSO/Okta domain before entering credentials, and rely on enterprise browser or password-manager controls that refuse to auto-fill credentials on a domain that doesn't match the saved legitimate URL.

5Real-time adversary-in-the-middle relay of MFA codes
What happened

The phishing kit relayed captured credentials instantly, via a Telegram channel, to the attacker, who logged into the real portal and triggered a genuine one-time code; the fake page then re-prompted the victim for that code, relayed it in turn, and the attacker used it before expiry, defeating SMS and TOTP-based MFA.

The control that would have stopped it

Deploy phishing-resistant MFA (FIDO2/WebAuthn hardware security keys with origin binding) instead of SMS or TOTP codes. Cloudflare showed this is the one control that stops this exact relay technique even after credentials are already phished.

6Optional remote-access payload
What happened

In some flows, once a victim had submitted both credentials and MFA code, the phishing page pushed the AnyDesk remote-access tool, which would have given attackers direct control of the victim's machine had it been installed; Cloudflare's Cloudforce One team documented this fallback step.

The control that would have stopped it

Enforce endpoint controls and application allowlisting that block installation of unsanctioned remote-access software such as AnyDesk.

7Access, data theft, and downstream pivot
What happened

With valid sessions or credentials, attackers reached internal and customer-support systems (as at Twilio and Mailchimp), harvested customer data, and used that vendor-side access to attempt account takeovers at the vendors' own customers, such as re-registration attempts on Signal accounts and password-reset attempts on DigitalOcean accounts, completing the objective of broad, monetizable access across a supply chain.

The control that would have stopped it

Apply least-privilege access to customer-support tooling, monitor for anomalous internal system access, and rotate credentials and terminate sessions immediately on suspected compromise, so a vendor breach cannot silently cascade into its customers' accounts.

Quick Facts
Victim
130+ organizations including Twilio, Cloudflare
(attempt, not breached), Mailchimp, and Klaviyo; downstream victims included Signal, DigitalOcean, and Twilio's Authy users.
Location
Primarily United States
(114 of the 136 corporate email domains were U.S.-based or had U.S. staff); also Canada and other regions
Date
March 2022 to August 2022
(Group-IB disclosure August 25, 2022; Twilio breach detected August 4, 2022; Cloudflare attempt July 20, 2022)
Impact
No consolidated dollar figure publicly disclosed; impact measured in credential/data theft
BasisunquantifiedNo consolidated figure; impact stated in credentials, MFA codes and affected customers
(~9,931 credentials, 5,441 MFA codes), 209 affected Twilio customers (Twilio's final October 27, 2022 figure, revised up from the 163 reported in its August 24 interim update), 93 compromised Authy accounts, and 1,900 Signal phone numbers exposed.
Status
Documented incident
Case Type
Real-World Incident
Sector
Financial Services & Insurance, Retail & E-commerce, Technology & Software, Telecommunications
Threat Actor
Organized Crime
Explore more

Related Cases

Browse by what this case has in common with others in the library.