Skip to content

About Conisec

Conisec is an independent publication covering crypto security incidents, exploits and regulation — with a verification step on every story.

Last reviewed

Conisec covers the part of crypto that most publications treat as an afterthought: what breaks, who it hurts, and what the rules say about it. We are a security and compliance desk, not a price site. We do not publish market calls, and we do not run price predictions.

Why we exist

When an exchange halts withdrawals, a bridge is drained, or a regulator publishes a new licensing regime, the people affected need three things quickly: an accurate account of what happened, a clear statement of who is exposed, and a way to check their own position without taking anyone’s word for it. That last part is usually missing. Conisec exists to supply it.

The Ledger

Every security, incident and regulatory story we publish carries a fixed four-line panel called The Ledger:

  • What happened — one factual sentence, with its primary source.
  • Who’s exposed — which users, chains, contracts or jurisdictions.
  • How to verify — the exact check you can run yourself.
  • What changes — what is materially different as of today.

The Ledger is descriptive and procedural. It is not financial, legal, tax or security advice, and it never tells anyone to move funds. Read our methodology for how each line is sourced and verified.

What we will not do

We will not invent an incident, a loss figure, a CVE, a contract address, a regulator statement or a date. We will not attribute an attack to a named actor without an official attribution. We will not publish a “recovery” or “revoke” link we have not verified against the project’s own channel. We will never ask you for a seed phrase, a private key, a signature or a wallet connection — for any reason. The full list is in our editorial guidelines.

Who writes this

Conisec is at the start of its publishing life. Rather than present a masthead we do not have, we will name every contributor as they join, with a real photo, a real biography and verifiable credentials. Factual records compiled by the newsroom — Incident Tracker entries, jurisdiction field sets, sourced timelines — publish under the Conisec Staff byline, and what that byline means is explained in our editorial guidelines. Analysis and post-mortems carry a named author. We do not publish under “admin”.

Corrections

We append corrections; we do not quietly rewrite. Every correction is dated on the article itself and listed on our public corrections log. If you have found an error, or an incident we have missed, tell us.