The Briefing

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

Showing 25 to 48 of 71 briefings

Tuesday 6 October

Breaches and Incidents6 Oct 2026

ASOS confirms the 10am notification was unauthorised, cites third-party platforms and does not name Snowflake

The channel is confirmed and the Snowflake claim is not addressed. What the RNS says and leaves out, what UK GDPR and UK MAR say, and what to do about every platform that can message your customers.

Breaches and Incidents6 Oct 2026

Bromcom found a legacy sign-on breach on 6 September; its first dated public post came 18 days later

A superseded sign-on service stayed in production because an internal system still called it. Bromcom found the breach on 6 September, posted on 24 September, and by 30 September called the central question ongoing.

Monday 5 October

Breaches and Incidents5 Oct 2026

Microsoft's X account: two unauthorised posts, 47 minutes apart by our arithmetic, and no word on the cause

Microsoft's 13-million-follower X account carried a disclaimer that told readers to trust only official channels, and Microsoft says it did not write it. The minutes, what is not stated, five routes in, and a UK checklist.

Breaches and Incidents5 Oct 2026

About 9,000 spoofed Nikkei emails reached news sources among others; who was exposed is not yet counted

What Nikkei's notices say in Japanese and English, what they leave out, how Japanese and UK law treat the security of data held for journalism, and an ordered checklist for any organisation that holds the names of sources or whistleblowers.

Breaches and Incidents5 Oct 2026

Frontline's breach letters were first reported 48 days after it found the flaw, and name no software

A supplier to US school districts found a flaw on 14 August and was first reported notifying districts on 1 October, 48 days later. Staff Social Security numbers were taken; the product, the counts and the actor are not stated.

Breaches and Incidents5 Oct 2026

Denmark says one company's lawful access reached 8.8 million of the 11 million entries in its CPR register

About 80 per cent of the register, more than the population, reached through one company's lawful access. What the ministry and Datatilsynet state, what CPR's own terms say about controls, and the checks a UK team can run.

Breaches and Incidents5 Oct 2026

Korea's bank breaches: AI use is unconfirmed on the record, and the faults described are old ones

Shinhan, KB Kookmin and Hana name about 25,000, 99 and 89 customers. The AI-tool claim rests on a vendor researcher's page-title reading and an anonymous official; on the record it is 'cannot be ruled out'. What is stated, what is not, and a UK checklist.

Saturday 3 October

Breaches and Incidents3 Oct 2026

DTU deletes former users' addresses after six months, not their CPR numbers, and holds about 160,000 of them

Four in five of DTU's up to 200,000 are former users, and the six-month deletion covers addresses, pictures and next of kin, not the CPR number. What the notice states, what it leaves out, and the checks a UK team can run.

Thursday 1 October

Breaches and Incidents1 Oct 2026

KillSec takedown: five servers and 110 TB seized, but no release says how victims will be told

Three provisional arrests, five servers, five domains and 110 TB, in a case led from Hamburg with one arrest in the UK. The counts do not match, and no release describes how victims will be told or what happens to files already published.

Breaches and Incidents1 Oct 2026

Kiteworks published 125 advisories. None says which one, if any, is the shutdown flaw

The 10.0 flaw has a CVE, a score and a fixed version. The flaw Kiteworks said it found during the shutdown has none that any record attaches to it, and no advisory in the batch says whether it is there.

Breaches and Incidents1 Oct 2026

By our count, MetaMask Staking queued 7,066 Lido validators to exit hours before its notice, naming no cause

The beacon chain shows 226,112 ETH of Lido stake queued to exit 6 to 12 hours before MetaMask's first notice. The notice and Lido's post name no cause, no count and no key status, and no funds lost are reported.

Breaches and Incidents1 Oct 2026

DIVD was breached through two Zammad flaws. One has no fix on record, and the AI claim is no stronger

Ten days on, DIVD's breach has a root cause: two Zammad flaws, one with no fix on record. The evidence for an AI agent is still tempo and comments in scripts, and the Zammad finding does not add to it.

Page 4

Thursday 1 October

Breaches and Incidents1 Oct 2026

The Pentagon's breach letter is dated 64 days after the flaw was found, and says accessed, not stolen

The Pentagon's personnel data centre dated its breach letter 64 days after discovering the flaw, after at least 258 days of access. What the notice states, what it leaves out, and the checks a UK team can run.

Wednesday 30 September

Breaches and Incidents30 Sept 2026

SlowMist logs Bitget attacker activity from 31 August, Mandiant dates access to 24 September, neither names a product

Two forensic documents published on 30 September add a longer chain, two products, a web shell and a custom withdrawal tool. SlowMist's logs start on 31 August, Mandiant dates the appliance access to 24 September, and neither names a product, vendor or CVE.

Breaches and Incidents30 Sept 2026

Microsoft's Titan skipped the token signature check: 17.3 trillion rows counted, two sampled

Faav's write-up counts 17,333,335,124,315 rows from metadata and describes two one-row samples. The endpoint was locked down 4 days after the report, the bounty was $5,000, and Microsoft edited the only account.

Breaches and Incidents30 Sept 2026

France's tax authority learned of the theft 49 days after it began, from the thief's own claim

The French tax administration took 49 days to learn of a theft made with stolen staff passwords, and only from the attacker's own post. What the ANSSI report establishes, what it leaves out, and the checks a UK team can run.

Tuesday 29 September

Breaches and Incidents29 Sept 2026

DIVD says an AI agent hacked it. Its evidence is tempo and code comments, and the flaw is still unnamed

The record as of 29 September: an intruder that decided each step at machine speed, explained itself in code comments and fought its own tools. The flaw, the attacker, the model and the data outcome are all unstated.

Breaches and Incidents29 Sept 2026

Elsevier's domain record sat unchanged for 342 days, yet three of its addresses went to a LAPSUS$-branded page

A redirect changes where a name points, and the public record shows the registration layer stayed still. What is missing is the layer that moved, the real length of the window, and anything beyond Elsevier's own "no indication".

Breaches and Incidents29 Sept 2026

Bitget says it found the root cause on 25 September. It described it three days later and names no product

Bitget's account moved from a compromised backend system to a flaw in an unnamed third-party security product. The two are layers of one chain, not rivals, but the wording around them keeps shifting and the report that would test it is late.

Breaches and Incidents29 Sept 2026

ShinyHunters: the official record was 105 words on 28 September. On 29 September the Dutch police published a full statement

The record moved in a day: a 40 word police post became a full statement with two suspicions, a custody ruling and a statement that the man was not arrested over Odido. The FBI claim is still a claim, and nothing official links the two.

Breaches and Incidents29 Sept 2026

Keio says trains ran, but customer forms went unreadable at least seven hours before it confirmed the attack

Keio's first notice named no company. The group's own pages describe failures in payments, loyalty points, bookings, commuter-pass sales and inbound mail, while trains are reported unaffected and nobody has given a restoration date.

Breaches and Incidents29 Sept 2026

Kiteworks says it fixed a critical flaw. It has published no CVE, score or version

A 55-word notice and a press release close the Kiteworks shutdown. Neither carries a CVE, a score or a fixed version, and the vendor's own advisory register has nothing newer than 27 May 2026.

Breaches and Incidents29 Sept 2026

Times Car confirms 6.6 million breached accounts, at most 1.65 times the 4 million members it announced in August

Times Car's parent says about 6.6 million accounts were breached, against a membership of more than 4 million announced in August. The notices name the data and the dates, and leave cause, attacker and headcount open.

Breaches and Incidents29 Sept 2026

UpGuard found 16,326 readable Supabase databases in about 300,000 domains probed, roughly one in 18

UpGuard probed about 300,000 Supabase-using domains and found 16,326 with readable tables, about 5.4 per cent. Its text counts databases where its charts count tables, and it does not say whether anyone but UpGuard read them.