Editorial template

Incident Desk: how security reports will be handled

This is a reporting framework, not a report about a specific incident. No unverified incident claim is published here.

Every published incident explainer will separate:

  1. Confirmed facts: official notices, primary statements, independently reviewed evidence, and dated updates.
  2. Claims not yet confirmed: clearly attributed and never presented as fact.
  3. Who may be affected: stated plainly, including when scope is unknown.
  4. What users can do now: safe, reversible defensive steps based on the evidence.
  5. What remains unknown: visible uncertainty rather than speculation.

Required source & update block

Reports will list direct sources, access dates, the publication time, the last update time, and a correction log. Reputable reporting may provide context, but it does not replace primary confirmation.

Safety boundary

Incident explainers will not publish exploit instructions, request wallet details, promote recovery services, or turn a breach into investment advice. Readers should use official provider channels and independently verify links.

Updates & corrections

When this standard changes, the page will receive a revised date and a plain-language explanation. Specific incident reports will identify their primary sources and distinguish what is known from what is still being checked.