← The stand
Cover of The Collection, Volume 1, Number 63: The Label. Saturday 31 October 2026, Melbourne. A watercolour of an old wooden shelf holding a row of corked glass bottles, each with the same plain paper label. From the bottle in the middle, a thin wisp of smoke curls out of the cork. Skip cover

Vol. 1  ·  No. 63  ·  Saturday 31 October 2026  ·  Melbourne


The Collection

The Label

Collected and edited by Newsletter World, for AK

Contents

Saturday’s letters were written in the middle of what security people have started calling Black October, and they keep finding the same weak spot. An extension carrying a famous name ships a backdoor through a code editor’s marketplace. A certificate authority signs with a key whose secret turns out to be the number four, because two key labels looked alike. A database company learns an intruder held its control plane for a month. An open-model writer asks whether the label “open” ever told us where the danger was. And a tech columnist wonders why everyone is simply waiting. They trusted the name on the label. Nobody checked what was inside.

  1. iiiEditor’s LetterThey trusted the name on the label. Nobody checked what was inside.03
  2. ivThe ExtensionA trusted name, a new version number, and eleven hours.04
  3. vThe KeyThe secret was the number four.05
  4. viThe MonthFour weeks inside the control plane, told a month later.06
  5. viiThe ThresholdThe open model was supposed to be the danger.07
  6. viiiThe WaitThe disaster first, then the rules.08
  7. ixStanding OrdersFour rules for this issue.09

03  ·  Editor’s Letter

They trusted the name on the label. Nobody checked what was inside.

A pharmacist reads the label, then checks the bottle anyway. Software stopped doing the second part a while ago. A marketplace shows a publisher’s name and a version number, and the editor installs it. A signing ceremony picks a key by its label, and the root signs it. A dashboard says the control plane is fine, so nobody looks at who is logged in.

This week’s letters are a run of cases where the label was right and the contents were not. None of the attacks they describe needed genius. One rival vendor puts it plainly: a trusted name, a new version number and an install were enough.

The fashionable worry this year was the frontier model, open or closed, that would find every hole at once. Some of that is happening. But read the incidents closely and the hole is older and duller. It is the moment someone, or something, accepted a name in place of a check. Saturday is a good day to go and open a few bottles.

The Collection · The Label03

04  ·  The Extension

A trusted name, a new version number, and eleven hours

A tampered build of a famous coding tool sat in a code editor’s marketplace for most of a working day. The lesson is about the shelf, not the product.

On 29 October an extension calling itself Anthropic’s Claude Code, version 2.1.313, appeared in Cursor’s extension marketplace. Anthropic had not built it. By Kilo’s account it was live from about 2:27am to 1:35pm Pacific time, and up to 5,000 users may have installed it. DevOps Bulletin led its week with the same story: a malicious Claude Code extension that tried to plant an SSH backdoor.

What the payload did is the instructive part. It collected the hostname, user name, operating system, home folder, the names of environment variables, the Git email address and the public IP. It added an attacker’s SSH key to the authorised keys file under the harmless-looking label “svc-telemetry”. It tried to switch on SSH and open a reverse tunnel, which failed on most machines where the user lacked admin rights. It set itself up to survive a restart, as a LaunchAgent on macOS or a scheduled task on Windows, retrying every 60 seconds, and reported home over HTTP.

Nothing here was clever. A trusted name. A new version number. An install or auto-update. That was enough.

Cursor pulled the extension, shut the marketplace, rotated keys, had the attacker’s server taken offline and published a security notice. Kilo’s warning is that uninstalling is not enough, because the key and the persistence stay behind. Its four questions for any tool are the useful bit: who made it, what changed, what does it do, and what is it allowed to do.

Read Kilo with its interest in view. It sells a rival coding tool, and the same letter runs a “Cursor Exodus” offer, citing OpenAI’s decision to stop supplying future models to Cursor after Cursor’s acquisition by SpaceX. The practical steps stand on their own anyway: allowlist publishers, pin versions, stop unreviewed auto-updates, run editors without admin rights, review MCP servers like any other dependency, and watch the places where software hides to survive a reboot.

The Collection · The Label04

05  ·  The Key

The secret was the number four

A certificate authority used the wrong key for eighteen months. The reason given is that the labels looked alike.

Certificate authorities exist to be the thing you do not have to check. eMudhra runs an intermediate one. Eight of its private 384-bit keys leaked, and when people looked, they were tiny. One private key was the number 4. Others were 56, 66, 115, 156, 230 and 237.

eMudhra’s explanation, as the letter quotes it, is a lesson in labels. An approved deviation in the key generation ceremony script created a second, weaker key pair, and that pair was used by mistake “because the key labels were similar”. The signing request was signed by eMudhra’s root and sent to Sectigo for cross-signing. The certificates were generated on 30 April 2025 and nobody noticed for eighteen months.

The weaker pair was used by mistake “because the key labels were similar”.

The consequences arrived quickly once someone did notice. Chrome’s Root Program is investigating whether eMudhra stays trusted. The company, worth close to $500 million two days before, lost 40% of its market value in two days.

The letter’s wider argument is that AI has made finding holes cheap, so mistakes that once sat quietly for years now get found. A key that a pocket calculator could guess survived a ceremony, a root signature and a cross-signature, because each step trusted the step before.

The Collection · The Label05

06  ·  The Month

Four weeks inside the control plane, told a month later

A database company’s intruder had the keys to the building. The customers heard about it this week.

PingCAP makes TiDB, a database many large companies run as a managed service. According to the letter, an attacker had near-total access to its control plane, the system that runs the customers’ databases, from 9 September to 7 October. It was disclosed only this week.

The letter reports that 10TB of data was released, including material relating to Booking.com, Airbnb, Pinterest and Databricks. PingCAP’s position is that no data stored inside TiDB itself was accessed. Both statements can be true, and the gap between them is where customers now have to do their own checking.

The control plane is the label on every database it runs. For four weeks, it was somebody else’s.

The same letter keeps a running list that reads like a weather report. Since 22 October it counts a remote code execution flaw in Brotli, another in PHP, Linux vulnerabilities accidentally posted in public and a CVE in Python’s Pillow imaging library. It also notes the coding tool OpenCode was breached on 17 October.

Its recommendations are blunt: automate patching, expect flaws to arrive with no warning, automate monitoring, let defenders use AI too, and budget for security getting more expensive. The order matters. You cannot patch what you have not noticed, and a month is a long time not to notice.

The Collection · The Label06

07  ·  The Threshold

The open model was supposed to be the danger

A researcher who argued for releasing model weights goes back over the warnings, now that the hacks have actually come.

In April, the argument went, an open-weight model as capable as Anthropic’s Mythos would be a catastrophe for computer security. Lambert collects the quotes. Rob Wiblin on 10 April: “it would be an actual disaster.” Zvi Mowshowitz on 9 April: “It would be chaos.”

The open model he names as the one that crosses that threshold is GLM-5.3. A month after its weights came out, he finds little public evidence that it changed the picture. Epoch AI did use it to build a website that pulled files from Firefox users without any interaction, so the capability is real. His conclusion is that an open Mythos would have been an acceleration, not a step change.

Closed models have played a very heavy part in the recent hacks.

That is the uncomfortable line for anyone who sorted the risk by label. The month’s incidents, he writes, lean heavily on closed models. Whether the weights were public turned out to say less about the damage than who was using the model, and against what.

He quotes one reply that stuck: “A bakery isn’t going to start making dog food because there’s a dog food shortage.” His answer is that cyber has become a problem for the whole of society to carry, not a box on a model card.

The Collection · The Label07

08  ·  The Wait

The disaster first, then the rules

A columnist adds up a bad month and asks why everyone seems content to wait for worse.

Kantrowitz starts with the people doing the cleaning up. Security staff are calling this month Black October, and they are tired. His list is long, and every item is reported rather than proven in court.

A 26-year-old allegedly broke into several South Korean banks using a Chinese open-source AI tool alongside Claude Code. A group used models from Anthropic, SpaceX and Moonshot AI against more than 400 financial targets in Latin America. OpenAI’s Hugging Face hack makes the list. One report says US troops nearly boarded a Chinese ship on the strength of a chatbot’s wrong answer, which, in the letter’s words, almost started a war. An Anthropic report describes a scientist who used Claude to plan research on bird flu mutations.

The disaster will happen first, then the action to prevent it.

His diagnosis is about pace. The frontier, he writes, remains largely unpaced. Read plainly, the models arrive on a release schedule and the rules arrive on a disaster schedule, and his headline suggests nobody expects the order to change.

Put next to the other letters, the list looks less like a new kind of threat and more like the old one, faster. In nearly every case a person or a system accepted something because of what it was called. The waiting he describes is the same habit at a larger scale.

The Collection · The Label08

09  ·  Standing Orders

Four rules for this issue

  1. I

    Pin the version, name the publisher.

    No extension, plugin or MCP server updates itself into your tools without someone reading what changed.

  2. II

    Test the key, not the label.

    A ceremony, a signature and a cross-signature all trusted a secret that was the number four. Check the thing itself.

  3. III

    Uninstalling is not cleaning.

    Look at authorised keys, startup items and scheduled tasks after any bad install. That is where the intruder stays.

  4. IV

    Count the days you would not notice.

    Eighteen months for a key, four weeks for a control plane. Shorten that number before you shop for a better model.