Security / privacy Creators on X (Twitter): 90 Indexed

This is the pool of Security / privacy creators on X (Twitter) within Software — 90 of them. The narrower the niche, the higher the reply rate; searching broadly for "Software creators" usually spends budget on audiences that do not overlap yours.

How this slice differs from the index as a whole

• 92% have recent content captured for judgement versus 46% overall — better-evidenced than average.
• A and B grades are 74% of this slice versus 37% overall — a denser pool, so the same screening effort yields more usable names.
• 29% publish an email or IM handle against 6% index-wide — easier to reach directly than average.

How to read these numbers: this covers creators indexed and validated inside Koinon Link, not every creator on the platform. Suspected bought-follower accounts are quarantined and excluded from the table above (shown separately). The authenticity score is our own anomaly detection over follower/engagement structure, not a platform-official metric. Figures update as collection continues.

Creators in this slice

• The Hacker News (@TheHackersNews) — New unpatched vulnerabilities and CVEs

• Florian Roth ⚡️ (@cyb3rops) — Vulnerability exploitation detection and post-exploit forens

• TCM Security (@TCMSecurity) — PNPT certification and exam prep

• heise online (@heiseonline) — Cybersecurity vulnerabilities and incidents

• Parler (@parler_social) — Parler ecosystem and integrated tools

• mRr3b00t (@UK_Daniel_Card) — agentic security

• zCloak Network (@zCloakNetwork) — AI Agent Trust Protocol

• Docteur Hippocrate (@DocteurPEB1) — Bypassing surveillance with VPNs

• MarsCat (@MarsCat_Global) — Decentralized Web3 infrastructure

• Sentinel (@SentinelP2P) — dVPN reliability and adoption

Ordered by follower tier, first 10 shown. Each link opens that creator’s public profile: what they post about, who reads it, and recent samples — no contact details.

Top 6 countries

Why this niche deserves its own view

"Security / privacy" is defined by who the audience is and what job they do, not by what the creator posts about. Two creators can both cover AI tools while their audiences barely overlap — one talks to media buyers who care about creative and bids, the other to engineers who care about APIs and deployment. Searching by topic mixes them together; searching by audience function does not.