AI Weekly Malaysia

A quoted excerpt from Anthropic's Frontier Red Team reports that on 100 randomly selected tasks from an internal Binary Exploitation benchmark, GLM-5.3 produced full control flow hijacks in 4% of trials and Claude Mythos Preview in 6%. The team notes that earlier models — Claude Opus 4.6 and GLM-5.2 — succeeded in none of the trials, framing this as a crossed threshold in the spread of advanced cyber capabilities. The post is collected as a short quotation by Simon Willison; no benchmark harness, mitigations, or task details are included in the text.

Why: If your agentic coding setup relies on the assumption that the model cannot write working memory-corruption exploits, that assumption no longer holds for at least two models named here (GLM-5.3, Claude Mythos Preview), while the prior generation (GLM-5.2, Opus 4.6) scored zero. That is an argument for sandboxing shell, file, and network access on capability grounds rather than on 'the model probably won't'. Treat the 4% vs 6% gap cautiously — the excerpt gives no methodology, so it supports the direction of change, not a precise ranking.

Simon Willison posted a short comment pointing to a Hacker News thread titled "GPT 6.1 Sol: Near-Astra intelligence for a fifth of the price," published 29 September 2026 alongside his live blog of the OpenAI DevDay 2026 keynote. He notes the pelican-riding-a-bicycle SVG output for GPT-6.1-Sol is "not notably different from the GPT-6 family" pelicans. The excerpt contains no model specs, benchmark numbers, or actual pricing figures — only the headline claim and a link.

Why: There is nothing concrete here to act on: no price, no context window, no benchmark, no availability date. The only usable signal is Willison's pelican test showing no visible capability jump over the GPT-6 family, which is a weak reason to re-evaluate model routing or budgets. If you are choosing models this week, wait for the linked HN thread and DevDay live blog rather than acting on the title's "fifth of the price" claim.

Tom's Hardware reports on a Chainalysis report finding blockchain-assisted cyberattacks up more than fivefold since last year, driven mainly by North Korean and Iranian state actors and Russian-speaking criminal groups. The technique, called Blockchain Dead Drops (BDD), stores malicious payloads in on-chain transactions and smart contracts so infected devices can retrieve them on demand from public, censorship-immune blockchains rather than from servers that can be seized or blocked. The excerpt also claims open-weight LLMs are linked to an increase in attacks, but cuts off mid-sentence before any supporting detail.

Why: The concrete operational change named here is payload hosting moving off takedown-able servers onto public chains, which means incident response that relies on blocking domains, IPs, or seizing C2 infrastructure may not remove the payload source. If your detection stack only watches HTTP/DNS egress, BDD retrieval traffic is a different channel you have not instrumented. Note that the open-weight LLM claim is asserted in the headline but the excerpt ends before showing the evidence, so do not repeat it as fact.