zkSecurity

• Name: zkSecurity
• URL: https://zksecurity.xyz/
• Category: cryptographic-security R&D company / zero-knowledge audit-report operator / reproducible ZKP-vulnerability-dataset steward
• Tags: zero-knowledge security-research
• Summary: zkSecurity belongs in companies/, not only projects/, because the useful question is not just what audit report or zk bug corpus exists? but which named operator turns cryptographic review, public writeups, reproducible exploit datasets, and first-party ZK tooling into workflow truth other protocol teams may start depending on? The practical leverage is not only advisory prestige; it is who chooses which proof-system failures get turned into reusable public lessons, what cryptographic-review posture becomes normal, and how much downstream teams inherit zkSecurity’s reports, zkbugs corpus, and technical explanations as living assurance infrastructure.
• What it does:
  • Performs security reviews for zero-knowledge protocols, cryptographic algorithms, smart contracts, consensus systems, and adjacent cryptographic infrastructure
  • Maintains a public reports portal spanning circuits, consensus components, cryptographic libraries, and protocol integrations, which makes report publication itself part of the reusable ecosystem knowledge layer
  • Publishes zkbugs, a reproducible dataset of real-world ZKP vulnerabilities across multiple DSLs and proving stacks, turning one-off audit findings into a reusable test and education corpus
  • Develops open-source cryptography and ZK tooling such as Noname, Wasmati, and other engineering artifacts that extend the company boundary beyond point-in-time review work
  • Publishes deep technical writeups, such as its Groth16 setup-collapse analysis and Reclaim circuit-design post, that convert concrete audit or incident work into broadly reusable failure-mode guidance
• Key claims:
  • zkSecurity’s public materials frame the team as a security R&D group specializing in advanced cryptography rather than a generic audit boutique
  • The reports portal shows a substantial first-party archive across Aptos Confidential Assets, Ethereum Foundation PeerDAS KZG libraries, Risc Zero Helios, Celo Self, Hyperlane’s Aleo integration, DarkFi, Penumbra, and other cryptographic or proof-heavy systems
  • The zkbugs repository says it includes 139 vulnerabilities with reproducible examples across Circom, Halo2, Cairo, Bellperson, Arkworks, PIL, Gnark, Plonky3, and Risc0, which is strong evidence that zkSecurity is packaging reusable assurance infrastructure rather than only delivering private review services
  • The public blog and incident-style technical notes show zkSecurity turning proof-system failures into explicit operational guidance, including the Groth16 gamma == delta setup-collapse family that later mattered across Veil and Foom Cash
  • The GitHub organization profile also highlights expertise across ZKP, MPC, FHE, and post-quantum cryptography, which reinforces that the company boundary is methodological and research-heavy rather than tied to one narrow product SKU
• Whitepaper: No classic standalone zkSecurity whitepaper is the important artifact here. The most useful primary materials are the public reports portal, GitHub organization profile, zkbugs repository, and technical writeups; the existing source bundle in ../whitepapers/zksecurity-primary-sources-2026-05-07.md remains the best compact capture.
• Sources:
  • https://zksecurity.xyz/
  • https://reports.zksecurity.xyz/
  • https://github.com/zksecurity
  • https://raw.githubusercontent.com/zksecurity/.github/main/profile/README.md
  • https://github.com/zksecurity/zkbugs
  • https://raw.githubusercontent.com/zksecurity/zkbugs/main/README.md
  • https://blog.zksecurity.xyz/posts/reclaim/
  • https://blog.zksecurity.xyz/posts/groth16-setup-exploit/

Internal linkages

• Strong adjacent company reads: trail-of-bits, chainsecurity, and informal-systems.
• Useful proof-facing companions where the reusable lesson matters more than the firm name: trusted-setup-finalization-and-verifier-family-quarantine, verification-key-statement-inventory-and-asset-reachability-discipline, and proof-facing-field-domain-canonicalization-discipline.
• Concrete incident anchors where zkSecurity’s public technical work materially sharpened the corpus: veil-cash-groth16-delta-gamma-setup-collapse-forged-withdrawals-2026-02-21 and foom-cash-groth16-delta-gamma-setup-collapse-whitehat-rescue-2026-02-26.

Protocol / company boundary

• There is no especially useful standalone zkSecurity protocol doing the analytical work here.
• The meaningful surface is a company-run cryptographic-assurance shell: which audits become public, which bug classes get turned into reproducible datasets, which proof-system failures are explained well enough to become ecosystem review checklists, and which first-party tools teams inherit as part of serious ZK engineering.
• That is why zkSecurity belongs in companies/: the control question is who curates, publishes, and operationalizes this research-and-review workflow, not what neutral protocol primitive supposedly replaces that judgment.

Control surface

• Practical leverage sits in report-publication choices, vulnerability-dataset curation, bug-taxonomy framing, proof-system failure interpretation, methodology branding, and the first-party tools or writeups teams begin to treat as authoritative review infrastructure.

• Even without direct onchain keys, zkSecurity can shape what sophisticated teams consider standard ZK audit coverage, what artifact families get fleet-wide scrutiny, and which cryptographic implementation mistakes become legible quickly enough to prevent repeats.

• Read zkSecurity as a cryptographic-assurance and public-research company first, not as a neutral protocol primitive.

• Last reviewed: 2026-08-07 UTC