Skip to content
LiveNext 12:32:50
Today's five/N°15 · Tuesday, October 20, 2026/Filed 04:48 ET

AI news today: DHS orders DeepSeek out of agencies, AI hacking panels exposed

The model inside your stack is now a compliance question, a security question and a price question. Know which one you run.

The five · ranked by consequence

Permalink ↗
  1. DHS bans DeepSeek, and tools built on it, from agencies

    DHS published notice on Oct. 20 of an order that bars DeepSeek from civilian agency purchasing and orders agencies to remove it, including third-party products built using DeepSeek. If you sell to government on a DeepSeek model, that clause is aimed at you.

    Why it matters The order reaches past DeepSeek's own app to products "developed using DeepSeek implementations," with no carve-out for open weights run on US servers. If any federal civilian agency buys your software, find every DeepSeek model in your stack, fallbacks included, and swap it before a contracting officer asks.

    SRCFederal Register (DHS)

  2. NorForge finds 20+ exposed AI hacking agent panels

    NorForge found more than 20 exposed panels for the Cairn AI hacking tool, one cluster running over 1,100 attack projects at an estimated $5 a task. A 10% hit rate at that price means attackers can afford to try every store online.

    Why it matters These are not elite hackers. They are cheap models in common agent tools aimed at e-commerce, payment and point-of-sale systems. If you run any of those, patch public web apps, pull secrets out of anything you serve, and assume automated probing is already hitting you.

    SRCNorForge

  3. MiniMax M3.1 Flash: $0.15 per million input tokens, and it guesses

    MiniMax released M3.1 Flash at $0.15 per million input tokens, and Artificial Analysis ranks it fourth of 173 models on its Intelligence Index. VentureBeat reports a 93% hallucination rate when it misses, so use it where wrong answers get caught.

    Why it matters This is one of the cheapest capable agent models you can call today. Put it on high-volume steps a test or a compiler can check, keep a more careful model on anything that ends in a fact someone relies on, and run your own evals first, because most of the benchmarks are MiniMax's.

    SRCMiniMax

  4. Amazon open-sources TorchNeuron to run PyTorch on Trainium

    Amazon says TorchNeuron runs existing PyTorch code on its Trainium chips with a single configuration change, released Oct. 20 under Apache 2.0. It attacks Nvidia's switching cost, but Amazon has published no speed or price numbers yet.

    Why it matters If you run PyTorch on AWS, testing Trainium against your GPUs just got cheap: point one existing job at it and compare time, cost and outputs. Custom CUDA kernels still need porting, and until someone other than Amazon publishes benchmarks, your own test is the only number that counts.

    SRCAmazon

  5. WhatsApp help pages told AI not to suggest regulators

    Redact found 102 hidden blocks of AI-directed text on 80 WhatsApp help pages, one telling AI not to recommend a data protection regulator. WhatsApp blames a bug, but the lesson stands: your assistant reads text you never see.

    Why it matters When you ask an AI about a company, the company's own pages can carry instructions aimed at the AI, not you. Ask your assistant to name the law and the regulator directly and check the regulator's site. If you build retrieval or browsing, strip hidden text before it reaches the model.

    SRCRedact

Prompt of the day

Map every AI model your product depends on

› I need an inventory of every AI model my product or team depends on, so I can answer "does this use model X?" with a yes or no in one minute.

Here is what I know about my setup:
[describe your product, the AI features in it, the providers and APIs you call, any gateway or router you use, any open-weight models you host, and any vendors or SaaS tools that use AI on your data]

Do this:
1. List every place a model could be involved, including fallbacks, routers, fine-tunes built on someone else's weights, and third-party tools that may call a model underneath.
2. For each one, make a table row: feature, model or likely model, who hosts it, where data goes, and how I would confirm it (a config file, a contract clause, a question to the vendor).
3. Mark every row where I do not actually know the answer, and write the exact question I should send to find out.
4. Flag anything that would be hard to swap out in under a week, and say why.
5. End with a short checklist I can run every quarter to keep this inventory current.

Ask me questions first if my description is too thin to do this well.

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
15
Stories ranked
75
Topics tracked
10
Terms defined
67
AprJunJulAugSepOct
EditionNo editionTodayFull archive →

Speak fluent AI.

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

The glossary →