#lastpassbreach
Live, measured metrics for the hashtag #lastpassbreach from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #lastpassbreach
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-29 19:17 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-29 19:17 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 19:17 UTCEverything below is measured over the latest 40 public posts (spanning ~19215 hours).
Posting hours (UTC) — busiest: 00:00
Languages: English (37) · German (3)
Avg boosts / post: 1.6
Top of the latest posts
If you are or have been a #LastPass user, we recommend changing the email addresses you had used for the accounts affected, and replacing them with SimpleLogin aliases. This way, even if it turns out a particular account of yours was compro
Nice read from The Verge on the #LastPassBreach: “The #LastPass disclosure of leaked password vaults is being torn apart by security experts” Quoting Jeremi Gosney @epixoip, Jeffrey Goldberg @jpgoldberg and yours truly. https://www.theverge
The #lastpassbreach has been weighing heavily on my mind since the most recent announcement. I was lucky enough to score an interview with @boblord from CISA to get his take on all of this. Tune in Monday for our chat and my recommendations
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/lastpassbreach