The Briefing

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

AI-generated conceptual airport illustration: waiting aircraft beneath a network of teal and amber routes; not a photograph of the incident.

Breaches and Incidents9 Sept 2026

NATS fixed the flight-processing system. The airport disruption kept moving.

The system was restored on 8 September. The aviation network still had a backlog to clear. A sourced timeline and worked recovery example explain the gap.

An antique brass wax seal stamp on its side beside a set pool of deep red sealing wax, both blank, on a dark surface lit by a cold indigo rim light.

Breaches and Incidents1 Sept 2026

Hundreds of fraudulent Pix transactions, and nothing was forged. The only sum Google names is tens of thousands.

Google reports Breeze Comet running two waves of fraudulent transactions through Brazilian payment systems. The count is a victim’s, the only money figure is in a different section, and no rail validates intent.

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.

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.

Dark server corridor with one rack glowing neon red against cold blue light

Breaches and Incidents21 Jul 2026

Ransomware playbooks keep failing at the same step: recovery

Ransom demands are collapsing and backups are working. Average recovery cost still rose 11% to $1.7m, and JLR lost five weeks of production for a modelled £1.9bn. The money moved from the ransom to the restore.

Breaches and Incidents21 Jul 2026

Half of breaches now involve a third party. Every clock starts too late

A 72-hour clause is not a control, it is an accounting mechanism. The clock starts at the vendor's awareness, which is the one variable your contract cannot set.