AI Weekly Malaysia

OpenAI said it disrupted a coordinated 'adversarial distillation' campaign that manipulated model interactions to reproduce protected reasoning in visible form, without breaking encryption or accessing stored conversations. The activity started July 1, 2026, spiked on July 24–25 to 16,000 attempted requests from over 4,000 users using one extraction pattern, expanded to related prompt-pattern activity across more than 15,000 users, and was fully shut down July 28. OpenAI attributed a 'core cluster' to individuals associated with Moonshot AI (described in the article as a Beijing-based Chinese AI company) without publishing technical evidence, and separately closed a pathway that let someone replay another user's encrypted reasoning to recover its contents.

Why: If your app logs or reuses reasoning traces from a hosted model — to fine-tune a cheaper student model, build an eval set, or cache outputs — you are in the exact pattern OpenAI banned accounts over, and 'we didn't scrape it, we just called the API' is not a defence. The closed replay pathway plus the August 2026 finding that encrypted reasoning traces are 'fully compatible and interchangeable across different sessions, users, and models within a provider's ecosystem' means the encrypted-reasoning feature should not be treated as a security boundary in your architecture. Treat vendor attribution claims (here, no technical evidence published) as unverified when you write your own threat model or compliance notes.