#exploitdevelopment
Live, measured metrics for the hashtag #exploitdevelopment from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #exploitdevelopment
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 · mas.to (Mastodon public tags API) · fetched 2026-09-29 16:02 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-09-29 16:02 UTCNo related tags with measured usage found for #exploitdevelopment.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-09-29 16:02 UTCEverything below is measured over the latest 40 public posts (spanning ~32800 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (38) · French (1)
Avg boosts / post: 2.7
Top of the latest posts
I implemented Ken Thompson’s Reflections on Trusting Trust (1984 Turing Award Lecture) compiler #backdoor for the GNU Compiler Collection (GCC). The backdoor maintains persistence by re-injecting itself to any new versions of the compiler b
I once had a dilemma: I had found a stack buffer overflow from a system I could only access in highly restricted environment. Yet I wanted to develop a proper #exploit for it. Reversing revealed that the #vulnerability itself was a really s
Exploiting Reversing (ER) series: article 09 | Exploitation Techniques: CVE-2024-30085 (part 03) Today I am releasing the nineth article in the Exploiting Reversing Series (ERS). In “Exploitation Techniques | CVE-2024-30085 (Part 09)” I pro
#exploitdevelopment across platforms
every network with a public tag surfaceFollow #exploitdevelopment 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/exploitdevelopment