#queuejumper
Live, measured metrics for the hashtag #queuejumper from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #queuejumper
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 15:42 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 15:42 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 15:42 UTCEverything below is measured over the latest 21 public posts (spanning ~5564 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (20) · German (1)
Avg boosts / post: 1.2
Top of the latest posts
@VitorHSSousa and myself have developed a #nmap service probe to identify whether a service on port 1801 is #MSMQ. I've just published it on the URL below. We can't guarantee this will successfully detect every version, but we've tested wit
Just checking in on all the MSMQ vulnerabilities in 2023 including #QueueJumper - from honeypots, I didn’t see a single exploitation attempt, just scanning. There also still isn’t a proof of concept exploit that reaches remote code executio
Four months passed since the publication of #MSMQ #QueueJumper. Has anyone seen any in-the-wild exploitation yet? #vulnerability #threatintel
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/queuejumper