#salty2fa
Live, measured metrics for the hashtag #salty2fa from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #salty2fa
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-28 05:33 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-28 05:33 UTCNo related tags with measured usage found for #salty2fa.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 05:33 UTCEverything below is measured over the latest 9 public posts (spanning ~2855 hours).
Posting hours (UTC)
Languages: English (9)
Avg boosts / post: 0.7
Top of the latest posts
❓How should SOC teams respond to the Salty2FA–Tycoon2FA hybrid? ⚠️ When activity from one #phishing kit suddenly drops, defenders should be ready for a surge in the other, likely controlled by the same operators. How to stay ahead: ✅ Treat
🚨 A new PhaaS “chimera” is making phishing attribution harder. #Salty2FA and #Tycoon2FA, once separate phishing kits, now appear inside the same campaigns and even the same payloads. 👾 See analysis of a hybrid payload: https://app.any.run
🚨 New threat alert: #Salty2FA & #Tycoon2FA are now targeting enterprises in a joint #phishing operation. We've found a hybrid #PhaaS that steals corporate logins at scale. Get all the details and actionable IOCs to not miss the attack ⬇️ h
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/salty2fa