The “incident” is doing a lot of work
Across all three pieces, the event is a “cyber-security incident” [1] or “cybersecurity incident” [3], which “affect[ed] some IT systems” [1]. The company’s own phrase, “certain of its IT systems” [2], is repeated almost verbatim by the BBC [1] and The Independent [2][3]. Nobody is named as having done anything. An incident is something that happens, like a delay or a spillage.
This is a small Newspeak move: a noun that absorbs the verb and the agent. “Incident” can mean a breach, an extortion attempt or a precaution that proved unnecessary. The BBC does note that criminals “seek[ing] to extort money by threatening to release customer data” [1] have hit other fashion brands, but it does not say that TFG’s case is one of these. To its credit, it adds that it is “too soon to ascertain” how the TFG incident occurred [1]. That caveat is honest. It also means the headline category, “hit by cyber-attack” [1], is a little ahead of the facts the piece can support.
Weather, buses and alarm calls
The commentary is where the framing gets vivid. A Check Point executive says attacks “are starting to look rather like buses… you wait for one, and suddenly three come along at once” [1]. The Independent quotes an investment strategist on “an onslaught of cyber attacks” and a “spate of infiltrations” that “should serve as a brutal alarm call” [2].
Buses, onslaughts and spates are metaphors of chance and natural arrival. Nothing in the bus image asks who built the timetable. The BBC also quotes a lecturer saying brands are “firmly in the crosshairs” [1] and that “No organisation is immune” [1]. If no one is immune, no one is especially responsible. Orwell’s complaint about political language was that it makes lies sound truthful and gives “an appearance of solidity to pure wind.” The wind here is mostly benign, but the effect is the same: the passive grammar of inevitability.
There is a tension the BBC leaves unresolved. The same article quotes Wilson saying “the retail industry has some serious questions to answer about how exposed its systems have become” [1], which is the opposite of weather. It is an accountability claim. It appears after the bus metaphor and is never followed up with what those questions are or who should ask them.
The reassurance loop
Companies’ reassurances are carried in near-identical form. TFG says there is “no reason to believe that payment information is at risk” [2][3], and the customer email says it did “not believe customers’ payment information had been affected” [1]. H&M says “we have not found any indications that our data environment has been compromised” [1][2]. These are statements about belief and about what has been found so far, in investigations that are still running. Repeated without comment, they work as a soothing Huxleyan background hum: calm, courteous, apologetic (“we apologise for any disruption” [1][3]).
The best evidence that reassurance can run ahead of facts is inside the BBC piece itself. Asos initially suggested “basic contact details” might be accessed, and later “hackers had obtained more detailed personal information” than first stated, after BBC News relayed what the criminals told it [1]. The Independent, by contrast, still reports Asos’s account as “some personal data, including names and contact details” [2][3] and does not mention the later update. Within this small sample, one outlet corrected the record and two articles from the other repeated the earlier, narrower version. We cannot say whether The Independent knew of the update; that is speculation.
The list as a genre
The Independent’s explainer [2] is useful as a ledger: JLR’s five-week shutdown and revenue fall of “more than £1 billion” [2]; M&S “forced to stop all online sales for about six weeks” [2]; Manchester Airport Group’s 8.7 million customers’ data [2]. These are concrete costs. Yet the format is a catalogue of victims, with “hit by hackers” as the recurring verb. The attackers appear as brand names (ShinyHunters, Scattered Spider) and the companies’ security choices barely appear. One wording choice stands out: the headline calls these “UK companies targeted,” although TFG is described as South African and H&M as Swedish [2]. That is a minor point, but it shows how loosely “UK retail” is being used as a frame.
Worth noting: the BBC calls the Asos push notification an “unprecedented” move that turned an app into a “ransom note” [1], attributed to unnamed “cyber-security experts.” That is a striking claim with no named source, and we could not check it.
What a reader would need instead
- The plain verbs: who accessed what, how, and what has been confirmed versus claimed. “Incident” should be replaced by the facts as soon as they exist.
- A clear separation of company assertions (“we do not believe”) from verified findings, plus follow-up when they change, as with Asos.
- A named regulator or tracker. The Independent says TFG “reported the incident to the relevant UK authorities” [3] but never names them. Readers should be told which body that is and whether it publishes breach notifications.
- Commentators who are asked the accountability question, not just the metaphor. Wilson’s “serious questions” [1] deserve answers, not a bus.
Without those, the coverage is accurate in its details and still teaches readers to treat repeated breaches as weather.
