Hacken primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Homepage

  • URL: https://hacken.io/
  • Key takeaways:
    • Hacken positions itself as an end-to-end blockchain security and compliance partner for digital assets rather than as a narrow smart-contract audit vendor
    • The homepage markets a broad lifecycle: architecture design, code review, protocol security, penetration testing, compliance support, proof-of-reserves work, and post-deployment monitoring
    • The homepage metrics are notable because they frame Hacken as scaled infrastructure: 1,671 public security assessments, 3,084 critical-to-medium vulnerabilities prevented, and $430B+ in assets verified across PoR audits

2) Docs portal overview

  • URL: https://docs.hacken.io/
  • Key takeaways:
    • The docs portal explicitly says it covers methodologies, workflows, audit preparation guidance, and technical endpoints
    • The docs enumerate methodology areas well beyond smart contracts, including blockchain protocols, cryptography audits, CCSS, DORA, proof of reserves, tokenomics, ISO 27001, and VARA
    • This is a strong signal that Hacken should be cataloged as broad security-and-compliance infrastructure rather than only as an audit marketplace or code-review shop

3) Public audits API

  • URL: https://docs.hacken.io/rest-apis/get-audits/
  • Key takeaways:
    • The GET /audits page says no authentication is required to use the Audits API
    • The schema exposes structured fields for audit names, clients, dates, repositories, commits, report links, severities, project links, and even audited-contract deployment metadata
    • This matters because it shows Hacken is not only publishing PDFs; it is also exposing reusable security data that can plug into external workflows and tooling

4) Public audit portfolio

  • URL: https://hacken.io/audits/
  • Key takeaways:
    • The portfolio page foregrounds aggregate stats such as total audits, total audited companies, secured market cap, and found vulnerabilities
    • Even though the page is partly dashboard-like, it reinforces the scale of Hacken’s public report corpus and the degree to which audit output is part of the product surface
    • The portfolio page pairs naturally with the public API docs, strengthening the view that Hacken operates a security-data layer in addition to a services business

5) HackenProof GitHub organization

  • URL: https://github.com/hackenproof
  • Key takeaways:
    • The public org shows activity around the HackenProof bug-bounty platform and adjacent tooling such as report encryption artifacts and bounty-program lists
    • This provides primary-source evidence that Hacken also participates in community/coordinated vulnerability-disclosure workflows, not just private audits
    • The GitHub surface is comparatively small, but it still helps confirm the broader ecosystem around the Hacken brand

Whitepaper / technical-doc status

  • No canonical Hacken whitepaper or litepaper surfaced in this pass.
  • The most useful primary sources were the homepage, the docs portal, the public audits API page, and the public audit portfolio.

Research notes

  • Best current category for the library: blockchain security / compliance / audit infrastructure / proof-of-reserves and public-security-data platform.
  • The key insight is that Hacken’s public API and audit corpus make it look meaningfully more like operational security infrastructure than a traditional consulting-only firm.
  • Its compliance framing also matters: the official materials stretch from code security into regulated control frameworks and reserve attestation.