A breach page is useful when it tells you what to do before the news cycle moves on. This topic collects dated incident write-ups, each separating what the company confirmed from what is still unconfirmed, with checks you can run on your own accounts, storage and hosting. Most start with the same step: rotate what the affected system could read.
What matters right now
- ConnectWise Cloud Backup (SkyKick) app credentials were abused in 160+ Microsoft 365 tenants, according to Huntress. ConnectWise posted its advisory on 16 October 2026; the write-up covers disabling the app and which Entra logs to read.
- Google's 6 October 2026 post says the .gh, .sl and .as registries were hijacked and unauthorized HTTPS certificates were issued. A CAA record and Certificate Transparency alerts limit what a rogue issuer can do for your domain.
- PwnEscape is CVE-2026-99999, a Linux kernel flaw published on 15 October 2026. Fixed kernels differ per branch, and a fix only applies after the host reboots.
- Railway's 21 October disclosure says secrets may have been decrypted. Rotate everything the platform held for you.
Where to start
- If you deploy on Railway, begin with the step-by-step rotation order.
- If your company runs Microsoft 365 through a backup or MSP vendor, read the ConnectWise SkyKick tenant check.
- If you manage TLS for a country-code domain, see how to set CAA records after the registry hijacks.
- If you run Linux hosts or sandboxes, PwnEscape and the fixed kernel versions lists what to ask your host.
- If customer uploads sit in cloud storage, checking S3 buckets for passport and KYC files takes you through Block Public Access and access logs.
- If your team uses GitHub, the Meta breach checklist covers sessions, tokens and audit logs.
- If a .env file may be public, start with what to do first when an env file is exposed.
- If you want the wider picture, the 2026 incidents timeline dates each event with its source.
Red by run.cloud offers a free scan that reads the stack your site serves and matches versions to known vulnerabilities, one per domain, no card.