---
title: "Twitter API data exposure"
description: "What the retained public evidence establishes about the Twitter / X 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/twitter-api-data-exposure-2022"
markdown_url: "https://www.ally.security/incidents/twitter-api-data-exposure-2022.md"
stix_url: "https://www.ally.security/incidents/twitter-api-data-exposure-2022/stix.json"
---

# Twitter API data exposure

API vulnerability allowing phone/email-to-account lookup. 200M+ account records scraped and later leaked.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Social media
- **Operational impact:** 200M+ account records scraped and later leaked
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In Jan 2022 (disclosed), X experienced an incident in its social media environment. The retained source describes the attack path as follows: API vulnerability allowing phone/email-to-account lookup. [1](#source-1)

The documented consequence was: 200M+ account records scraped and later leaked. [1](#source-1)

## Impact

- Documented impact: 200M+ account records scraped and later leaked. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: API vulnerability allowing phone/email-to-account lookup. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- [T1190 — Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190/) — mapped from the cited behavior. [1](#source-1)

## Response

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

This account is bounded to [Update about an alleged incident regarding user data sold online](https://privacy.x.com/en/blog/2023/update-about-an-alleged-incident-regarding-twitter-user-data-being-sold-online). 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/twitter-api-data-exposure-2022/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Update about an alleged incident regarding user data sold online

official · X

<https://privacy.x.com/en/blog/2023/update-about-an-alleged-incident-regarding-twitter-user-data-being-sold-online>

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

Review the supporting structured claims.

1. **Resulted In · 90% confidence · current**  
   Twitter API data exposure: The retained source describes containment action intended to limit further access or disruption.
2. **Resulted In · 89% confidence · current**  
   Twitter API data exposure: API vulnerability allowing phone/email-to-account lookup.
3. **Affected Organization · 100% confidence · current**  
   Twitter API data exposure: X
4. **Resulted In · 100% confidence · current**  
   Twitter API data exposure: The reviewed source documents the twitter api data exposure involving X.
5. **Resulted In · 83% confidence · current**  
   Twitter API data exposure: 200M+ account records scraped and later leaked.
6. **Used Attack Technique · 90% confidence · current**  
   Twitter API data exposure: https://attack.mitre.org/techniques/T1190/

</details>