Hexens primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The official hexens.io pages were protected by a Cloudflare challenge during this pass, so clean first-party extraction from the website was not available.
• The clearest current source of truth was Hexens’ GitHub organization and repository network.
• Those repos jointly point to a broader security-and-research platform rather than a narrow audit-only brand.

Primary-source snapshots

1) Official website status

• URL: https://hexens.io/
• Key excerpt:
  • The site did not yield readable primary content in this pass because requests were met with a Cloudflare “Just a moment…” challenge.
  • This matters because it explains why GitHub became the main usable primary-source surface for this review.

2) GitHub organization overview

• URL: https://github.com/Hexens
• Key excerpt:
  • The org description says “Novel approach to cybersecurity.”
  • The popular repos include Smart-Contract-Review-Public-Reports, awesome-fhe-attacks, piller, glider-docs, and glider-skills.
  • That repo mix suggests Hexens operates across released audit work, cryptography/security research curation, static analysis, and analyst enablement.

3) Public audit reports README

• URL: https://raw.githubusercontent.com/Hexens/Smart-Contract-Review-Public-Reports/main/README.md
• Key excerpt:
  • The README says: “This repository containts the smart contract audit reports and security reviews performed by Hexens.”
  • It links back to https://hexens.io/ for more information.
  • Even though the README is brief, it makes clear that the public-reports corpus is an intentional first-party artifact rather than an unofficial mirror.

4) Public audit reports repository page

• URL: https://github.com/Hexens/Smart-Contract-Review-Public-Reports
• Key excerpt:
  • The repository page exposes a large list of report PDFs with client/project names such as 1inch, API3, Babylon, Celo staking, EigenLayer, Fuel Bridge, LayerZero, Polygon zkEVM, and others.
  • The breadth of the visible file list implies a substantial released review corpus spanning bridges, staking, infrastructure, and protocol code.
  • That breadth is a strong signal that Hexens functions as reusable ecosystem security infrastructure, not merely a small boutique with a handful of sample reports.

5) awesome-fhe-attacks

• URL: https://raw.githubusercontent.com/Hexens/awesome-fhe-attacks/master/README.md
• Key excerpt:
  • The README says the project is “A curated list of research, articles, tools, and resources focused on attacks against Fully Homomorphic Encryption (FHE).”
  • It says the compilation is intended for researchers, practitioners, and anyone interested in the security aspects of FHE.
  • This is a strong clue that Hexens is investing in security-research curation well outside generic smart-contract audit marketing.

6) glider-skills

• URL: https://raw.githubusercontent.com/Hexens/glider-skills/main/README.md
• Key excerpt:
  • The README says the project is an AI agent skill that teaches coding assistants how to write Glider queries for analyzing Solidity smart contracts, including “security vulnerabilities, labeling, and pattern detection.”
  • It explicitly says the project is “Built by Hexens.”
  • That shows Hexens publishing analyst tooling and agent-facing workflow enablement, not only audit PDFs.

Working conclusion

Hexens is best cataloged as web3 security-and-research infrastructure with a strong public audit-library and analyst-tooling footprint. The decisive evidence in this pass was the combination of a large first-party released-audit corpus, niche cryptography-research curation around FHE attacks, and Glider-related tooling for Solidity analysis. The main caveat is that the official website itself was blocked by a Cloudflare challenge during retrieval, so GitHub had to serve as the primary first-party evidence surface.