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.

OpenAI says it identified and disrupted a coordinated adversarial-distillation campaign, with activity first observed July 1, 2026, that manipulated model interactions to reproduce protected reasoning rather than breaking encryption or accessing stored user conversations. One technique copied encrypted reasoning from one conversation and asked a model in another conversation to decrypt and transcribe it. OpenAI reports spikes on July 24-25 of 16,000 requests using an extraction pattern from over 4,000 users, and says it fully disrupted related prompt-pattern activity across a cluster of more than 15,000 users by July 28; independent researchers also disclosed related cross-model and conversation-compaction issues that OpenAI confirmed were real.

Why: If you ship on frontier model APIs, this is a concrete list of patterns that got accounts disrupted: replaying encrypted reasoning blobs across sessions, asking one session to decode another's hidden reasoning, and abusing conversation-compaction paths. The 15,000-user cluster disrupted by July 28 shows enforcement was broad, not surgical, so agent frameworks that cache and re-inject reasoning traces should be reviewed before they look like extraction. Note the text gives no Malaysia or SEA detail, so there is no local angle to act on here.

Tom's Hardware reports that OpenAI says actors linked to China-based Moonshot AI ran a campaign to extract its models' hidden reasoning, logging 16,000 extraction requests across 4,000 accounts before being cut off, with attempts peaking at 16,000 users over two days. The article body available here is mostly paywall and newsletter boilerplate, so the concrete detail is limited to the headline and URL: the 16,000 requests, 4,000 accounts, and two-day peak.

Why: If you ship a product on top of someone else's model API, this is a reminder that reasoning traces are treated as protected output, not a free training resource — distillation-by-scraping is what the account cutoffs were for. Before you build a pipeline that logs or replays another vendor's reasoning output, check their terms; the enforcement lever is account and key suspension, which hits your users, not just your bill. There is nothing Malaysia-specific in the text, and no pricing, version, or policy detail was included, so treat the specific numbers as an unverified vendor claim rather than a settled fact.

Nvidia CEO Jensen Huang told CNBC's Squawk Box that AI distillation — training models on other models' outputs — is "competition," saying "you're allowed to test somebody else's products all you want." That directly contradicts U.S. Treasury Secretary Scott Bessent, who in July called distillation "theft" and threatened sanctions against overseas companies that use it to extract capability from U.S.-built models. U.S. officials are reportedly weighing measures against foreign firms that rely on distillation, making it a flashpoint in U.S.-China AI competition.

Why: If you fine-tune or train on outputs from U.S. frontier models, the rules for that are now contested at the cabinet level, not just in license terms. Bessent's July threat of sanctions against overseas companies is the concrete risk to plan around: know whether your training pipeline depends on another vendor's outputs, keep records of what data you trained on and under which terms, and consider whether you could substitute open-weight or licensed data if restrictions land. Note the article gives no dates, thresholds, or named enforcement mechanism yet — this is positioning, not a published rule, so don't restructure your roadmap over it today.

PewDiePie has unveiled an 'uncensored' AI model called Ajax that is built to run on home PCs, according to Tom's Hardware. In the same report, the creator says OpenAI banned him twice over the model distillation used to build the product. The article text available is almost entirely Tom's Hardware site navigation, so there are no details on parameter count, benchmarks, licence, hardware requirements, or any response from OpenAI.

Why: The one concrete, actionable claim here is that distilling from a closed API got the developer banned twice — if your pipeline trains on outputs from OpenAI or a similar provider, that account risk is the thing to check before you build a product on it. Separately, an 'uncensored' model meant for home PCs means no provider-side moderation: if you ship on top of it, you own the safety filtering yourself. Beyond that, this item has no verifiable specs, so do not plan anything around it yet.