The Briefing

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

Showing 73 to 76 of 76 briefings

Sunday 30 August

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.

Tuesday 21 July

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.

That is every briefing in this category