#authquake
Live, measured metrics for the hashtag #authquake from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #authquake
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 · mas.to (Mastodon public tags API) · fetched 2026-07-28 03:35 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-28 03:35 UTCNo related tags with measured usage found for #authquake.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-28 03:35 UTCEverything below is measured over the latest 7 public posts (spanning ~524 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 0.6
Top of the latest posts
I bet Microsoft's tolerance of outdated TOTP responses that gave rise to the #authquake vuln is their need to support hardware OATH tokens. Time drift is a real problem and most have no way of correcting it. Still, you'd think that rather t
Microsoft MFA Bypassed via AuthQuake Attack – Source: www.securityweek.com https://ciso2ciso.com/microsoft-mfa-bypassed-via-authquake-attack-source-www-securityweek-com/ #rssfeedpostgeneratorecho #CyberSecurityNews #Identity&Access #securit
Microsoft MFA Bypassed via AuthQuake Attack https://www.securityweek.com/microsoft-mfa-bypassed-via-authquake-attack/ #Identity&Access #AuthQuake #MFAbypass #Microsoft #MFA
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/authquake