#Storm2372
Live, measured metrics for the hashtag #Storm2372 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #storm2372
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-28 02:20 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-28 02:20 UTCNo related tags with measured usage found for #storm2372.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 02:20 UTCEverything below is measured over the latest 3 public posts (spanning ~1124 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.3
Used together with
Top of the latest posts
#Storm2372
NEW: 🚨 Russian APT Storm-2372 is using device code phishing to bypass #MFA in attacks against organisations in Europe and the US. Read: https://hackread.com/russia-storm-2372-hit-mfa-bypass-device-code-phishing/ #CyberSecurity #CyberAttack
Despite my issue with the headline (it isn't bypassing MFA as much as tricking the user into authorizing access), this is a real ATO vector, and many teams don't know they're vulnerable to it. Switching off Device Code Flow if not needed, p
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/storm2372