#exploitdev
Live, measured metrics for the hashtag #exploitdev from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #exploitdev
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-09-29 18:59 UTC1 uses by 1 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-09-29 18:59 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-29 18:59 UTCEverything below is measured over the latest 40 public posts (spanning ~25619 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (37)
Avg boosts / post: 0.9
Top of the latest posts
Just published a proof-of-concept exploit for CVE-2025-32463, a new Linux privilege escalation vulnerability affecting sudo discovered and disclosed by Stratascale about 2 weeks ago. The PoC is available on GitHub. A full technical writeup
Go beyond just using Metasploit – learn to build with it. This comprehensive 2nd Edition guides you with foundational commands through porting public exploits (Chapter 12), building your own modules in Ruby (Chapter 13), and even fuzzing fo
🚨 For the FIRST TIME EVER 🚨 🌍🔥 Corelan Heap — Istanbul, Turkey 🔥🌍 🤝 In collaboration with Hackers Academy 🧠 Windows heap internals 🪄 Precise heap layout control (Memorigami) 🛠️ Hands-on, real-world exploit scenarios 📍 March 23-26
#exploitdev across platforms
every network with a public tag surfaceFollow #exploitdev straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/exploitdev