Coming Q3 2026

Third-party pentest executive summary

An external penetration-test engagement against Infinihash production services is planned for Q3 2026. This page is a placeholder that documents the plan, the vendor shortlist, the scope, the methodology, and the deliverable timeline. The public executive summary will replace this page in Q4 2026.

Status: planning · Last reviewed: May 2026.

Where we are right now

Infinihash runs continuous internal scanning today. The Q3 third-party engagement adds an independent adversarial perspective on top of that baseline.

Pentest exec summary - coming Q3 2026 Engagement kickoff is targeted for the first week of Q3. The public executive summary (severity counts, classes of finding, remediation status, residual risk statement) will be published on this URL in the first week of Q4 once the report is finalised and the high/critical findings have been remediated or accepted.

Who we are evaluating

Five candidate firms are under review. Selection criteria: depth in regulated fintech / KYC / KYT, cryptographic and smart-contract competence, regulator-friendly reputation, ability to staff in the Q3 window. Final pick announced at engagement kickoff.

Trail of Bits Candidate

Best in class for cryptographic protocol review and smart contracts. Heavier price tag and longer lead time, but the deepest bench for our settlement and signing surfaces.

Doyensec Candidate

Strong web/app security firm; well known for browser, IAM, and SaaS engagements. Good fit for KYC / KYT API surface and the Next.js subdomains.

HalbornSec Candidate

Crypto-native pentesting and SOC2 readiness work, used by many CEXes and L2s. Fast turnaround, broad coverage, useful pairing with our on-chain components.

Hacken Candidate

Mid-market price point, regulator-recognised in EU; useful as a secondary opinion or for compliance-driven coverage (CER.live, proof-of-reserves, ISO 27001 alignment).

Spearbit + companion shop Candidate

Distributed-research model via Spearbit/Cantina for the contract layer, paired with a traditional web-app shop for KYC / KYT / Coordinator. Best coverage for spend, lower SLA certainty.

What gets tested

Five production services in scope; clear out-of-scope list will be in the SoW. All testing happens against staging clones of production with realistic data fixtures; production endpoints are touched only for limited authenticated-surface verification.

KYC API In Scope

FastAPI service powering kyc.infinihash.com. Document extraction pipeline, Prisma schema, S3 evidence store, retention/TTL/legal-hold, webhook signing, multi-tenant org isolation.

KYT API In Scope

FastAPI + Celery service powering kyt.infinihash.com. Address screening, sanctions ingestion pipeline, SAR/FinCEN export, multi-chain enrichment, public demo screen route.

MyAi Coordinator In Scope

OpenAI-compatible routing layer + agent registration, GPU agent secrets, JWT issuance, parallel job fan-out. Includes admin secret rotation and webhook surface.

Settlement portal In Scope

Marketing / lead-capture portal at clearbox.infinihash.com. Static SPA, embedded Typeform/booking flows, session handling, deep-link integrity.

Client compliance portal In Scope

White-label BSA/AML portal at tfc.infinihash.com. Tenant document ingestion, role-based access, KYT proxy passthrough, document upload validation.

Out of scope (initial) Phase 2

Hyperliquid basis dashboard (internal management host, read-only), network administration interface, internal infrastructure gateway, plex/frigate/homeassistant personal stack. May be added in a follow-on engagement.

How the test will be run

Three combined approaches over the engagement window. Daily standups with the lead tester; findings filed in real time so we can remediate inside the window rather than waiting on the final report.

Gray-box (with creds)

Tester accounts at each tier (anon, retail, admin, multi-tenant peer) plus source-code read access to KYC / KYT / Coordinator. Authorization / IDOR / privilege-escalation coverage.

Black-box surface scan

External recon against all public subdomains. TLS / headers / CSP, exposed admin panels, version-leak fingerprinting, public S3 bucket and webhook misconfiguration checks.

Dependency + supply-chain audit

npm / pip / Cargo lockfile review, image base inspection, GitHub Actions and deploy pipeline review (S3 / SSM / incus push paths), CI secrets audit, signing-key handling.

Deliverable schedule

Six-week engagement window with a fixed public-disclosure date. High/critical findings are remediated or formally accepted before the public summary lands.

MilestoneWhenOutput
Vendor selection + SoW signedQ2 W12Selected firm + scope confirmation
Kickoff + test-account provisioningQ3 W1Engagement begins
Mid-engagement readoutQ3 W3Interim findings list (private)
Draft reportQ3 W4Full draft, severity-classified
Remediation + retestQ3 W5 - W6High/critical fixed or accepted
Final report + public exec summaryQ4 W1Replaces this page

What we run today, between pentests

The third-party engagement is layered on top of an internal continuous-scan baseline. The most recent internal scan results are linked below.

Smart contracts

  • Slither - static analysis, every commit
  • Aderyn - secondary static analysis
  • Foundry invariant tests + 10M fuzz runs
  • Most recent run: 2026-05-17 scan

Services + infra