Last updated: November 19, 2026 · Statements issued November 1 to 16, 2026 · 5W Public Relations
In a 5W review of 14 company statements about cyber incidents announced November 1 to 16, 2026, eight placed the incident at a third party, five gave a figure for the scale of exposure, and seven gave readers a clear next step. The review measures what the statements said, not who was at fault, and it is a snapshot of a 14-statement sample.
What does the data show?
- Eight of 14 statements placed the incident at a third party: Uber, TSMC, Caribbean Airlines, SEGA, Singapore Airlines, Crédit Mutuel Arkéa, SMBC and Casinos Austria.
- Five of those eight named the third party, and the five trace to three firms: Amadeus (Caribbean Airlines, Singapore Airlines), Arara (SEGA, SMBC) and Fireworks.ai (Uber).
- Five statements gave a figure for the scale of exposure, in different units: email addresses, booking records, records and customers. Nine did not.
- Seven statements told readers what to do. One more, Singapore Airlines, described a step the company was taking itself and is counted as partial.
- Six statements contained an apology or an expression of regret in the text we read.
- Two clients reported that Arara revised its initial assessment: first no leak, then confirmed exposure.
Where did companies say the incident happened?
Eight of the 14 statements described the incident as happening at a third party, such as a vendor, cloud provider or service provider. Five statements described the company's own systems, one described a legacy system from a prior acquisition, and the table shows the full coding for each.
| Company | Where the statement placed the incident | Third party named | Figure for scale of exposure | Apology or regret | Clear next step for readers | Statement type |
|---|---|---|---|---|---|---|
| Uber | Third party (Fireworks.ai) | Yes | Not shown in excerpt | Not shown in excerpt | Not shown in excerpt | Excerpt |
| Maersk | Legacy system from a prior acquisition | Not applicable | Not shown in excerpt | Not shown in excerpt | Not shown in excerpt | Excerpt |
| TSMC | Third party (cloud service provider) | No | No | No | No | Full statement |
| Caribbean Airlines | Third party (Amadeus) | Yes | Not shown in summary | Yes | Not shown in summary | Summary |
| Coles | Own systems, cause not stated | Not applicable | No | Yes | No | Full statement |
| Amplifon | Own network | Not applicable | No | Yes (regret) | Yes | Full notice template |
| GitBook | Own infrastructure | Not applicable | No | Yes | Yes | Full statement |
| SEGA | Third party (ARARA) | Yes | Yes (2.2 million email addresses) | Not shown in summary | Not shown in summary | Summary |
| Singapore Airlines | Third party (Amadeus) | Yes | Yes (46,000 booking records) | Not shown in excerpt | Partial | Excerpt |
| Crédit Mutuel Arkéa | Third party (service provider platform) | No | No (declined to confirm a loss estimate) | Not shown in summary | Yes | Summary |
| Nitori | Own system | Not applicable | Yes (up to 37.62 million records) | Yes | Yes | Full statement |
| Vanderbilt University | Own systems | Not applicable | Not shown in excerpt | Not shown in excerpt | Yes | Excerpt |
| SMBC | Third party (Arara Inc.) | Yes | Yes (227,216 email addresses) | Yes | Yes | Full statement |
| Casinos Austria | Third party (external service provider) | No | Yes (about 150,000 customers) | Not shown in summary | Yes | Summary |
Source: 5W analysis of 14 company statements, November 19, 2026. Evidence links and key wording for every row are in Table 7.
Which statements gave readers a clear next step?
Seven of the 14 statements told readers, customers or staff to do or avoid something specific: Amplifon, GitBook, Nitori, SMBC, Casinos Austria, Crédit Mutuel Arkéa and Vanderbilt University. Vanderbilt told staff and students to shut down devices and not to click unfamiliar links. SMBC told customers not to click links or open attachments in suspicious emails.
Two coding decisions affect the count. Singapore Airlines said it was contacting customers with upcoming trips to change their booking reference numbers, which is a step the company takes, so it is coded partial and left out of the seven. Coles told shoppers that customers "are able to shop as normal," which says service continues but gives no step about the incident, so it is coded no. Coles did apologize and say it would post further updates, and those items are counted in their own columns.
Did Arara change its first answer?
Two clients reported that Arara revised its initial assessment. SMBC's notice says Arara reported on October 28 that its logs showed no leak, then confirmed on November 2 that email addresses had leaked. Press coverage of SEGA's statement says Arara told SEGA on October 29 that no data was compromised, then reported exposure on November 3. The SMBC account is from the company's own notice. The SEGA account is from a press summary.
| Client | Arara's first message | Arara's confirmation | Client's public statement |
|---|---|---|---|
| SMBC | October 28: logs showed no leak | November 2: leak confirmed | November 5, three days after confirmation |
| SEGA | October 29: no data compromised | November 3: data exposed | About November 9, six days after confirmation |
Source: SMBC notice dated November 5, 2026; BleepingComputer report on SEGA's statement, November 9, 2026.
What were the incident and disclosure milestones?
The milestones below show the start and end event for each row because the clocks measure different things, so this report does not average them. GitBook's gap runs from its internal alert to its public notice, while Uber's runs from a vendor notifying Uber to a press report of Uber's confirmation.
| Company | Start event | End event | Elapsed |
|---|---|---|---|
| GitBook | Internal alert, November 2, 18:10 UTC | Public notice, November 3, 13:15 CET | About 18 hours |
| Maersk | Ransomware group's claim, as reported by The Record | Maersk statement, reported November 12 | 3 days, per The Record |
| SMBC | Arara confirmed the leak, November 2 | SMBC notice, November 5 | 3 days |
| SEGA | Arara reported exposure, November 3 | SEGA statement, about November 9 | About 6 days |
| Uber | Fireworks.ai notified Uber, October 9 | Uber confirmation reported by TechCrunch, November 16 | 38 days (Uber had begun notifying drivers in some states earlier) |
Source: company notices and press reports linked in Table 7.
Case note: Amplifon's notice template says the company detected suspicious activity on February 11, 2026, and that a review on October 6, 2026 indicated recipients' information may have been impacted. The template is undated and contains unfilled placeholders, so it shows two internal milestones and does not measure a disclosure delay.
What reassurance wording did statements use?
Six statements used a hedged phrase such as "no evidence," and eight said a named type of data or system was not affected. Coles said it had "not identified any evidence" that customer, team or supplier data was compromised. TSMC said it had "no evidence" that its systems were compromised and described the leaked data as matching data held by a cloud service provider.
| Field | Definition | Count | Companies |
|---|---|---|---|
| Hedged phrase | Statement says "no evidence," "no indication" or "not aware of" about compromise, impact or misuse | 6 of 14 | TSMC, Coles, Amplifon, GitBook, SEGA, Maersk |
| Named data or system not affected | Statement says a named data type or system was not included, exposed or breached | 8 of 14 | SMBC, Nitori, Casinos Austria, Caribbean Airlines, Singapore Airlines, SEGA, GitBook, TSMC |
| Outside claim or estimate not confirmed | Statement declined to confirm, or did not address, a figure or claim made by someone else | 2 of 14 | Vanderbilt University, Crédit Mutuel Arkéa |
Source: 5W analysis of 14 company statements, November 19, 2026. A statement can fall in more than one row.
What should a cyber incident statement answer?
A communications team can check its own draft against five questions, and the 14 statements show how far the sample went on each. The sample is descriptive and does not show that any answer improves coverage, trust or legal outcomes.
| Question | What the 14 statements did |
|---|---|
| What happened? | Eight placed the incident at a third party and five of those named it. Five described the company's own systems and one a legacy system. |
| Who may be affected? | Five gave a figure for the scale of exposure, in units that vary. Nine gave none in the text we read. |
| What is still being verified? | Not coded as a field. Coles said it was "currently investigating," and TSMC said it was working to "ascertain the facts." |
| What should people do now? | Seven gave a clear next step and one gave a partial step. |
| When will they hear from us again? | Not coded as a field. Coles said it would post further updates on its website, and Vanderbilt said it would send updates throughout the week. |
Source: 5W analysis of 14 company statements, November 19, 2026.




