#log4shell_vulnerability
Live, measured metrics for the hashtag #log4shell_vulnerability from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #log4shell_vulnerability
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-27 12:12 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-27 12:12 UTCNo related tags with measured usage found for #log4shell_vulnerability.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:12 UTCEverything below is measured over the latest 2 public posts (spanning ~192 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
Impact of Log4Shell Bug Was Overblown, Say Researchers - https://www.redpacketsecurity.com/impact-of-log-shell-bug-was-overblown-say-researchers/ #threatintel #Log4Shell_vulnerability #Remote_code_execution #Software_exploitation
Lazarus Group Targets Log4Shell Flaw Via Telegram Bots - https://www.redpacketsecurity.com/lazarus-group-targets-log-shell-flaw-via-telegram-bots/ #threatintel #Lazarus_Group #Log4Shell_vulnerability #Operation_Blacksmith
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/log4shell_vulnerability