Corrections Policy
Effective October 10, 2026
Accuracy comes before speed. If a material fact is wrong, the article is corrected promptly and the change is described clearly.
What readers will see
A material correction names the fact that changed and carries the correction date. Small spelling or formatting fixes that do not alter meaning may be corrected without a note.
How to report a problem
Send the article title, the statement you believe is wrong, and a supporting primary source through the route listed on the Contact page. Every specific correction request is reviewed.
Correction log
- October 12, 2026 — Daiichi Kosho breach card: the timeline was corrected to match the company's own statement — malware was found October 1–2, the affected machine was isolated October 2, and the contractor reported the incident October 5 (the card previously gave different dates).
- October 12, 2026 — Denmark CPR briefing: wording that presented the incident's details as confirmed was revised, because the briefing's sources did not include a primary release from a Danish authority.
- October 12, 2026 — Console page: the Sony firmware 14.10 entry and the Nintendo firmware 23.0.1 entry were relabelled from CONFIRMED to REPORTED, because only secondary reporting was cited for them.
- October 12, 2026 — The briefing published as "Your password manager can't stop this attack" was retitled "Why signing out matters more than you think", and a section about online file converters was removed because it did not support the article's session-cookie point.
- October 12, 2026 — Briefing numbering: a gap in the briefing sequence was closed by renumbering the series, and the Denmark CPR report moved out of the numbered series into the breach tracker.
Substantive corrections are logged here with their dates as they are made.