#industroyer2
Live, measured metrics for the hashtag #industroyer2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #industroyer2
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 10:49 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 10:49 UTCNo related tags with measured usage found for #industroyer2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 10:49 UTCEverything below is measured over the latest 4 public posts (spanning ~618 hours).
Posting hours (UTC)
Languages: English (4)
Avg boosts / post: 2.5
Top of the latest posts
We're getting into "silly season" at the end of the year. With that in mind, I've thought about the things I did in 2022 that I found most interesting, helpful, or potentially impactful. First, there's the paper on #CTI-driven #ThreatHuntin
@kimzetter I'm honestly not sure? If that malware was designed to impact critical civilian infrastructure (eg, #Industroyer2), I'd say mitigating or defeating that represents a defensible, appropriate action given the targeting and intent.
There are similarities with previous attacks conducted by #Sandworm: a PowerShell script used to distribute the .NET ransomware from the domain controller is almost identical to the one seen last April during the #Industroyer2 attacks again
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/industroyer2