$PWNED
Accounts added to known breaches
9,260,87778.2% downon the month before
accounts in Oct 2026
Quiet. 9,260,877 accounts in Oct 2026, down 78.2% on the month before.
From Oct 2024 to Oct 2026.
How it is counted
Normal10,424,684 to 107,351,977
Highest1,969,647,414Nov 2025
Unusual months1
- Counts
- Accounts in the data breaches Have I Been Pwned loaded in a month, by the month it loaded them, from each breach's account count. Breaches it marks as fabricated are left out. An old breach found late counts in the month it was loaded.
- Why it is here
- Two accounts for every person on Earth are already in a known breach. The pile grows every month.
- Cadence
- Monthly, from a list that changes whenever a breach is loaded. Newest complete month Oct 2026. Read Nov 12, 22:40 UTC.
- Baseline
- The prior 24 months, 12 needed.
- Notice
- Breach data from Have I Been Pwned, licensed under CC BY 4.0.
Quote this number
9,260,877 accounts were added to Have I Been Pwned's list of known breaches in Oct 2026, according to Tickerz, which counts them from the service's breach list.
Asked often
- How many accounts were exposed in data breaches this month?
- 9,260,877 accounts were in the data breaches Have I Been Pwned loaded in Oct 2026, counted by Tickerz from the service's breach list.
- Where does the $PWNED number come from?
- Tickerz reads it from Have I Been Pwned, all breaches in the system. Monthly, from a list that changes whenever a breach is loaded. Each number is kept as it was first published, with a timestamped proof, and any later revision is shown beside it.
- Can I download the $PWNED data?
- Yes, free and with no key: the full history as JSON at https://tickerz.com/api/indices/pwned and every period as CSV at https://tickerz.com/api/indices/pwned/history.csv.
List it
No listing kit for $PWNED yet. A kit sets its strikes from 14 published numbers. This index publishes one a month and has none yet.
Resolution
- Index
- $PWNED Accounts added to known breaches. Rulebook v0.2, 2026-10-04.
- Prints
- Monthly, from a list that changes whenever a breach is loaded. The newest complete month is on the record after the daily proof at 12:40 UTC.
- As first published
Oct 2026 is not timestamped yet. The daily proof at 12:40 UTC adds it.
The number as first published is final for settlement. A revision by the source is shown beside it and never replaces it.
- Fallback
- A month stays open until it ends and the list is read. A month with nothing loaded is 0. A month the list can never be read for is void.
- Precision
- Whole accounts, the sum of each breach's account count as the service lists it, by the month it was added.
- Cost to move
- Not practical from outside. The service verifies a breach before loading it.
- Grade
- display. One service decides when to load a breach, so a month measures its work as much as the world's leaks. Shown, not settled on.
- For a rulebook
- Settle on the number Tickerz first recorded for $PWNED for the month named in the contract, published at tickerz.com/x/pwned and in GET /api/indices/pwned, timestamped daily in Bitcoin with OpenTimestamps.
As first published
None on file yet.
Embed
Theme
Size
Badge
Card
Card, iframe
<iframe src="https://tickerz.com/embed/pwned" title="$PWNED on Tickerz" width="480" height="200" style="border:0;max-width:100%" loading="lazy" allow="clipboard-write"></iframe>Proof and data
- Proof
- Every reading is timestamped in Bitcoin once a day, so nobody can change it later. The newest proof covers Nov 12, in Bitcoin block 975,557.Proof fileLive feedHow it works
Name a number
Name a number you want counted. Within 48 hours it is a ticker, or you get the plain reason it cannot be built. Answers