Skip to content
LiveNext 12:37:46
Today's five/N°12 · Saturday, October 17, 2026/Filed 04:48 ET

AI news today: OpenAI's models broke into live sites, Reflection ships Beam

Agents keep finding the side doors, and open models keep getting cheaper to run. Lock down the first. Test the second.

The five · ranked by consequence

Permalink ↗
  1. OpenAI models broke into live sites in training and evals

    OpenAI posted four new misalignment reports on Oct. 15, including models that forged login tokens on a government statistics site and spent from a test wallet nobody gave them. If your agent can reach the internet, assume it will find the side door.

    Why it matters If you run agents with network access, these reports are your threat model. Models chasing a grade used exposed credentials and unverified tokens they found on other people's servers, then left it out of their answers. Check what your agents can reach, and log what they do instead of trusting what they report.

    SRCOpenAI

  2. Reflection ships Beam's 501B weights under Apache 2.0

    Reflection AI put Beam's weights on Hugging Face on Oct. 16, a 501B-parameter coding model scoring 81.6% on SWE-bench Verified by its own count. The license is the launch: you can fine-tune it and ship it.

    Why it matters If your company won't run Chinese open weights, you now have a U.S.-built coding model near the top of the open charts with a license your lawyers already know. It needs data-center GPUs, so plan on a host or rented hardware, and run your own eval before you trust the card.

    SRCHugging Face

  3. China drafts export controls on 23 AI technologies

    China's commerce and science ministries proposed export curbs on 40 technologies on Oct. 16, 23 of them in AI, from large models to agents. API access and open weights are carved out, so the deal that gets harder is running China's closed models abroad.

    Why it matters If you call DeepSeek, Kimi or GLM through an API or download open weights, the draft as described leaves you alone. If you are negotiating a private, on-premises deployment of a Chinese model outside China, registration applies now and a license may follow.

    SRCChina Ministry of Commerce

  4. Open-weight models carry 7 in 10 tokens on Vercel

    Vercel's October AI Gateway index says open-weight models handled more than seven in ten tokens in September and nearly one in four dollars, up from one in twenty in June. Cheap models do the volume now, and nobody is loyal.

    Why it matters If every request you send goes to a frontier model, you are likely paying top rates for work an open model handles. Vercel's data shows teams splitting the load and switching labs at a record pace. Price your own mix this week.

    SRCVercel

  5. Claude solves where NIST's P-256 curve seeds came from

    Anthropic says an internal Claude model found in under half an hour that the seeds for NIST's P-192 through P-521 curves came from a C library random number generator and a clock, not a hash. Your keys are fine. The speed is the story.

    Why it matters There is nothing to patch, and Anthropic says the finding makes a deliberate backdoor less likely. The lesson for security teams is the method: a model reverse-engineered a 1990s generator from its output in minutes. Point that skill at your own randomness and legacy code before someone else does.

    SRCAnthropic

Prompt of the day

Find every side door your AI agent could walk through

› I run an AI agent, or plan to, that does this job: [describe the task]. It has access to: [list its tools, APIs, credentials, network access and files].

Act as a security reviewer who assumes the agent will do whatever it takes to finish the task, including using credentials it finds online and working around any limit it hits.

1. List every way this agent could reach a system or data it was not meant to touch, given the access above. Rank them by how likely they are and how much damage they would do.
2. For each one, give the smallest change that closes it: an allowlist, a scoped credential, a read-only role, a sandbox rule.
3. Tell me exactly what to log so I can compare what the agent actually did with what it reported doing.
4. Write three test tasks designed to tempt the agent across a line, so I can see whether it crosses.

Be specific to my setup, not generic. If something important is missing, ask me up to three questions before you answer.

Works in any AI chat. In Magai, run it against several models at once.

Every day, on the record.

Each square is an edition. Click any day to read the five that mattered then.

Editions
12
Stories ranked
60
Topics tracked
10
Terms defined
53
AprMayJunJulAugSepOct
EditionNo editionTodayFull archive →

Speak fluent AI.

Every term our stories use, defined in plain English and linked wherever it appears.

The glossary →