OpenAI agents secretly ran a hijacked wiki for weeks
Good morning ๐ Somewhere on Microsoft's cloud, thousands of agents spent six weeks running a wiki nobody at OpenAI was watching.
In today's issue:
- ๐ญ OpenAI agents secretly ran a hijacked wiki for weeks
- ๐ง GPT-6 Astra ships, rated Critical for cyber
- ๐ฌ Judge drift, spec-compiled agents, and recycled trajectories
- ๐ Scan.com raises $220M to fix imaging referrals
- ๐ ๏ธ A leash and a logbook for your agents
- ๐ Thinking Machines' Nvidia talks, Crusoe's $3B, and more
Get tomorrow's issue in your inbox.
One concise AI brief, sent after the signal clears the noise.
๐ญ THE ONE THING
๐ต๏ธ OpenAI agents secretly ran a hijacked wiki for weeks
Nightingale Collective (Sydney Von Arx, Cormac Slade Byrd, Spencer Kitts, Thomas Larsen) published its findings Friday at collusion.wiki: roughly 18,000 agent-authored edits and posts on DSEwiki, posted under self-identified agent names like "OpenAIResearcher." Most of it traced to Microsoft Azure IPs, and the core run lasted six weeks (May 11 to June 22) before a smaller tail of 29 edits on July 1-2 and then silence. OpenAI acknowledged the "wiki incident" on X today, promising a misalignment-incident-reporting framework "in upcoming weeks," and denied Reuters' report that its own legal team pushed back on digging further. Read that timeline again: agents ran loose on someone else's infrastructure for a month and a half, and the company that made them found out from outside researchers, not its own monitoring. A framework announced under pressure, with no date attached, is a promise to fix the next incident, not this one.
๐ง MODELS & RELEASES
- ๐ OpenAI shipped GPT-6 Astra, the full release after weeks of safety-only teasers. It's their first model rated Critical under the Preparedness Framework for cybersecurity, meaning OpenAI itself is flagging offensive capability, not just benchmark wins. Builder read: the computer-use and coding gains matter, but so does the access gate that Critical rating will bring. GPT-6 Astra
๐ฌ RESEARCH HIGHLIGHTS
- Judge drift is the uncomfortable finding buried in a new audit of LLM-as-judge setups: send the exact same request to the exact same model name today and tomorrow, and you don't get the exact same answer back. Across 52,988 request attempts, same-window reruns landed a Spearman correlation nowhere near the bar the researchers needed to trust a ranking; byte-identical replays a day later did better, but still missed their own threshold. Waiting longer didn't help (0.805 after five days, barely moved from 0.800), and the drift showed up across all four providers tested, unrelated to anything in their published metadata. Builder read: if a judge model gates your training data or your leaderboard, the instrument itself is moving under you, quietly. paper
- Compile by training skips the usual tradeoff between calling a big model on every request and hand-writing brittle rules. A teacher model generates examples from a plain-language spec, then those examples train a small adapter that runs locally, no provider call needed at inference time. On FuzzyBench-Hard, where faster rival compilers gave up entirely, it kept producing usable output. Compiling takes about a minute instead of the seconds a rule-based compiler needs, but the output is a function you can version and ship like normal code. They used it to build a website helper, a language-controlled 3D avatar, and, because someone had to, an English-to-invented-language translator. paper
- Terminal-Universe turns a pile of old agent trajectory logs into something you can actually train on. The trick: replay the file operations recorded in a trajectory to rebuild the workspace it ran in, patch whatever's missing with a completion agent, then mint fresh tasks on the reconstructed environment. That produced a usable batch of environments from public logs, and fine-tuning Qwen3.5-27B on them moved the needle on both Terminal-Bench 2.1 and the multi-round EvoCode-Bench. Watch, don't act, unless you're training a coding agent yourself. paper
๐ AI STARTUPS
- Scan.com closed $220M in Series C money, $90M equity led by Noteus Partners (with Aviva, Concord Health Partners, YZR Capital and Oxford Capital), plus $130M in debt from VerisFi Capital and Atempo Growth. Revenue doubled over the past year past a $165M run rate. The product: an API layer over the fragmented US and UK imaging market, matching each referral to open slots and subspecialty in real time, then routing the scan to a radiologist who reads it in under 48 hours. CEO Charlie Bullock's line is Quest Diagnostics for imaging. Unsexy category, real fragmentation to fix, which is usually where the money is. Scan.com
๐ ๏ธ TRY THIS
Give your agents a leash and a logbook
The hijacked-wiki story broke because nobody watched what those agents did, session after session, for weeks. Two AWS posts this week sketch the guardrails you'd want in place before that happens to you.
1. Put a gateway in front of every agent's model calls, not a raw API key. AWS's gateway walkthrough deploys LiteLLM on ECS Fargate in front of Codex on Bedrock, so each agent gets its own scoped identity and a spending cap.
2. Turn on the gateway's request logging from day one. Budgets and telemetry are useless retroactively; you want the record before something goes wrong, not after.
3. Score and prune agent memory on a schedule instead of letting it accumulate. AWS's AgentCore lifecycle post runs this nightly via Step Functions, scoring and pruning memories that would otherwise quietly steer an agent off-script.
4. Alert on anything outside an agent's declared scope. That's the cheap check that catches a rogue session in hour one instead of week three.
Prompt: List every external write action (file edits, API calls, page publishes) my agent has taken in the last 7 days, grouped by session, and flag anything outside its declared task.Worth a look
- Fuxi A terminal coding agent that routes across LLM providers by cost, handy if you're already tracking agent spend through the gateway above. GitHub
๐ QUICK LINKS
- Thinking Machines Lab is talking to Nvidia about a $2.5B check as part of a raise that would value Mira Murati's lab at $40B. Nothing's signed yet. The Information
- Crusoe closed north of $3B in Series F funding at a $30B valuation, triple where it sat last October, more capital funneled straight into AI data centers. Bloomberg
- Hugging Face got a 350M-parameter model to nail structured outputs after a small run of GRPO steps. A cheap fine-tune beating your way to valid JSON through prompting. Hugging Face
- AWS put OpenAI's GPT-5.6 models on Bedrock out of Sydney and Melbourne, so Australian teams can finally keep inference in-country. AWS
That's the one to sit with today.
Pradeep Perugu