Redbot Labs / Threat Intelligence
OpenAI Disrupts Coordinated Campaign to Extract Protected Model Reasoning
- Incident ID
- RBT-TI-0109
- Organization
- OpenAI
- Reported Location
- San Francisco, California, United States — Vendor Location
- Severity
- High
- Category
- Protected Reasoning Extraction / Adversarial Model Distillation
- Record Date
- 2026-09-30
Incident Summary
OpenAI reported disrupting a coordinated campaign that manipulated model interactions to expose protected reasoning. The company described the activity as adversarial distillation and said it did not involve broken encryption, a compromised database, or direct access to stored conversations.
What Happened
Coordinated extraction attempts
OpenAI observed 16,000 attempted extractions from more than 4,000 users on July 24–25. These counts do not represent confirmed successful extractions.
Campaign disruption
Investigation identified related activity across more than 15,000 users. OpenAI reported disrupting that cluster by July 28.
Attribution limits
OpenAI attributed a core cluster to individuals associated with Moonshot AI. That is the vendor’s assessment; it did not attribute every operator to one actor. OpenAI
Affected Systems
Protected Reasoning Outputs / Cross-Conversation Reasoning Handling
Attack Vector
Model Interaction Manipulation / Encrypted Reasoning Replay / Coordinated Extraction
Business Impact
Reasoning confidentiality
OpenAI closed a replay pathway requiring prior possession of another user’s encrypted reasoning. Its disclosure does not establish arbitrary access to other users’ conversations or successful cloning of a model.
Redbot Analysis
Treat reasoning artifacts as sensitive application data
Redbot Labs assesses protected-reasoning handling as an application security concern that extends beyond whether a model refuses a direct request.
Systems that store, transport, or reuse internal reasoning need explicit rules governing who can submit an artifact, which session may consume it, and what information may appear in the resulting output.
Encryption needs authorization controls
Encrypting an artifact protects its contents under particular conditions. Applications must also enforce ownership, intended use, session binding, expiration, and replay restrictions.
A component capable of interpreting protected data should not become an unintended disclosure route when that data is submitted through a different workflow.
Monitor coordinated behavior
Per-account limits can miss campaigns distributed across many accounts. Defenders should correlate repeated extraction patterns, shared infrastructure, and unusual artifact reuse while preserving legitimate research and normal usage.
Validate every delivery path
Security testing should cover streamed responses, conversation compaction, model transitions, tool outputs, and partner-hosted deployments. Controls should be tested wherever protected information can cross an identity or application boundary.
Sources
Protected Reasoning Extraction / Adversarial Distillation

