About
HubSec started from investigating bridge incidents in the Polkadot ecosystem. We kept finding the same patterns — insufficient proof validation, shallow authorization checks, missing boundary conditions on leaf indices. Different protocols, same classes of bugs.
We publish our analysis because the ecosystem gets safer when post-mortems are thorough, public, and specific enough to act on. A report that says “the bridge was exploited” doesn't help anyone. A report that traces the exact call path, identifies the missing check, and shows how to detect similar bugs before deployment — that's useful.
Every incident we investigate feeds back into our detection tooling. The Hyperbridge analysis produced three new Sentinel rules. The vulnerability taxonomy now covers 70+ classes across 10 attack surfaces. The goal is systematic: turn incident response into prevention infrastructure.
Focus
Polkadot-specific. We don't cover every chain — we go deep on Substrate runtimes, FRAME pallets, ink! contracts, XCM messaging, and the bridge infrastructure that connects it all.
Not affiliated with Parity Technologies, Web3 Foundation, or any protocol team we analyze. Our research is independent.
PGP: 1027 0DFF 53E0 B61F 809F C079 E0E6 BF50 4785 0199
HubSec Forensics provides on-chain intelligence and evidence packaging. Attribution analysis produces probabilistic assessments, not definitive identification. Timezone estimates, behavioral profiles, and entity resolution are investigative leads, not proof of identity. HubSec does not access off-chain personal data, IP addresses, or exchange KYC records. For identity confirmation and legal action, engage qualified legal counsel and law enforcement with the evidence package HubSec provides.