---
title: "Cloudflare blocked phishing campaign"
description: "What the retained public evidence establishes about the Cloudflare incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/cloudflare-blocked-phishing-campaign-2022"
markdown_url: "https://www.ally.security/incidents/cloudflare-blocked-phishing-campaign-2022.md"
stix_url: "https://www.ally.security/incidents/cloudflare-blocked-phishing-campaign-2022/stix.json"
---

# Cloudflare blocked phishing campaign

Same 0ktapus campaign. Attack failed due to hardware FIDO2 security keys.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Cybersecurity/CDN
- **Operational impact:** Attack failed due to hardware FIDO2 security keys
- **Financial impact:** $0 (attack blocked)

## What happened

In 2022, Cloudflare experienced an incident in its cybersecurity/cdn environment. The retained source describes the attack path as follows: Same 0ktapus campaign. [1](#source-1)

The documented consequence was: Attack failed due to hardware FIDO2 security keys. [1](#source-1)

## Impact

- Documented impact: Attack failed due to hardware FIDO2 security keys. [1](#source-1)
- Documented financial consequence: $0 (attack blocked). [1](#source-1)

## Timeline

### August 9, 2022 — Documented public update

The [The mechanics of a sophisticated phishing scam and how we stopped it](https://blog.cloudflare.com/2022-07-sms-phishing-attacks/) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Same 0ktapus campaign. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- **0ktapus** — identified in the supported attack description. [1](#source-1)

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The retained source describes containment action intended to limit further access or disruption. [1](#source-1)

This account is bounded to [The mechanics of a sophisticated phishing scam and how we stopped it](https://blog.cloudflare.com/2022-07-sms-phishing-attacks/). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/cloudflare-blocked-phishing-campaign-2022/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### The mechanics of a sophisticated phishing scam and how we stopped it

research · Cloudflare

<https://blog.cloudflare.com/2022-07-sms-phishing-attacks/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Affected Organization · 100% confidence · current**  
   Cloudflare blocked phishing campaign: Cloudflare
2. **Resulted In · 100% confidence · current**  
   Cloudflare blocked phishing campaign: The reviewed source documents the cloudflare blocked phishing campaign involving Cloudflare.
3. **Occurred At · 100% confidence · current**  
   Documented public update: 2022-08-09
4. **Resulted In · 90% confidence · current**  
   Cloudflare blocked phishing campaign: The retained source describes containment action intended to limit further access or disruption.
5. **Resulted In · 89% confidence · current**  
   Cloudflare blocked phishing campaign: $0 (attack blocked).
6. **Resulted In · 84% confidence · current**  
   Cloudflare blocked phishing campaign: Attack failed due to hardware FIDO2 security keys.
7. **Resulted In · 88% confidence · current**  
   Cloudflare blocked phishing campaign: Same 0ktapus campaign.

</details>