The Briefing

What happened, why it matters, and what to do about it. Analysis, not rewritten press releases.

Showing 589 to 600 of 654 briefings

Monday 31 August

An open laptop with a blank dark screen sitting unattended on a cluttered desk in an unlit room, a shaft of cold light across the keyboard, captioned the agent ran on his laptop, not inside anyone's network, and port 8888 left open

AI Security31 Aug 2026

Aurora ransomware drove an AI coding agent at 10 organisations. It ran on the operator's own laptop, and most commands failed first time

The agent was one pivot away, not inside. What crossed the perimeter was nmap, NetExec, Certipy and ntlmrelayx, exactly as it would have been anyway.

Two identical blank sheets of heavy cream paper on a dark desk, the top one curling to reveal the copy beneath, captioned DoJ corrected one copy, the other still says victims, one of two, and 17 articles never corrected at all

Threat Intel31 Aug 2026

DoJ corrected its China hacking claim. It fixed one copy of two, and 17 articles still carry the original

A correction that reaches one of two identical documents has not been made. Both copies are live on justice.gov and they say different things.

An airport car park barrier arm raised at night beside a weathered number plate recognition camera on its post, wet tarmac below, captioned two 72-hour clocks, only one of them started, and 8.7 million customers

Breaches and Incidents31 Aug 2026

Manchester Airports breach reaches 8.7 million customers. Two 72-hour clocks applied, and only one of them ever started

Gigabytes are not people. The verified finding is one authenticated record carrying far more than MAG disclosed, and a NIS duty that never engaged.

Sunday 30 August

A white electrical plug hanging loose in front of a dark wall socket, captioned: six critical flaws, NVD scored none of them. 0 of 8 identifiers independently analysed.

Breaches and Incidents30 Aug 2026

Six critical WordPress flaws in ten days. NVD independently scored none of them, and the claim that plugins cause most compromises has no current source

The 91% figure describes the vulnerability catalogue, not the cause of breaches. The only quantified entry-vector number anyone can cite is a 2016 survey of about 222 sites.

A brass mechanical counter drum caught mid-rotation in deep shadow, captioned: the fix went public, the chains heard last. 20 hours 5 minutes from that release to the first drain.

Breaches and Incidents30 Aug 2026

Cosmos Labs published the security fix 28 hours before it warned the chains. Six networks were drained of about $5.7 million

Cosmos Labs' own policy calls for private distribution before public disclosure on a network-wide risk. The advisory also never reached the global GitHub database, so no dependency scanner ever raised it.

A long blank unprinted paper roll coiling away into darkness, captioned: 284 million records, not 284 million people. 14.9% of revenue, in the units named.

Breaches and Incidents30 Aug 2026

ShinyHunters claims 284 million McKesson records. It is a row count, and the units McKesson named are 14.9% of the business

Every technical detail of this intrusion is single-sourced to the attackers. The one number McKesson has published points the other way.

A single glass tick box glowing cyan on a black background, captioned: eight stages in, not one is a CVE. 0 CVEs, no patch exists, because nothing is broken.

Threat Intel30 Aug 2026

TerminalFix chains eight stages from a fake CAPTCHA to a reverse tunnel, and never touches a CVE. There is nothing to patch

Every stage uses documented Windows behaviour, so there is no patch, no KEV deadline and no scanner finding. The controls that reach it had to be set before the lure arrived.

Saturday 29 August

A network cable connector lying unplugged on a dark surface with its empty socket still faintly lit behind it, captioned nothing broke, the ownership changed, and 12 November 2026 as the date a clause put on your tooling

AI Security29 Aug 2026

OpenAI is cutting model supply to Cursor after SpaceX bought it. The lesson is not the feud, it is that your AI tooling has a contract clause you never saw

Nobody using Cursor chose SpaceX. They chose an editor, and the ownership underneath it changed. Nothing technical broke.

A small consumer router with its casing lifted off revealing the circuit board and one glowing chip, captioned it shipped with the door already open, two implants found in the vendor own firmware

AI Security29 Aug 2026

Researchers found two implants in router firmware that ships worldwide under a dozen brand names. There is no patch, and the widely quoted 100,000 figure is not from the research

You cannot patch your way out of hardware you have no reason to trust. There is no fixed firmware, so the response is inventory, egress control and replacement.

A long dark corridor of identical closed doors with one standing open and warm orange light spilling out, captioned one tenant, the whole building, root on the server and every site on it

AI Security29 Aug 2026

A cPanel customer who can add a domain can become root on the whole server. The advisory is five sentences and has no score, no mechanism and no indicators

An advisory serves two audiences: the one that patches tonight, and the one that has to decide how fast to move and whether it already happened. This serves only the first.

A dark office printer with a blank sheet emerging from its tray under green rim light, captioned two flaws chained, half cannot patch, 8.8 plus 9.4 equals unauthenticated code execution

AI Security29 Aug 2026

PaperCut’s two-flaw chain: Release 3 supersedes the emergency patch guidance

Release 3 supersedes Release 2. Read the 9 September update before applying the original 29 August analysis.

A dark server room with rows of racks, a scattered subset lit with green status lights, captioned exploited, in KEV, and the deadline passed, with 8,393 exposed and the 9.8 described as a config setting

AI Security29 Aug 2026

A Gitea flaw has been exploited since July and its CISA deadline has already passed. The 9.8 depends on a setting you can change tonight

The fix shipped on 27 July in a routine release. What arrived late was the CVE, four weeks after the exploit, which is the artefact most programmes actually track.

Show 12 more