During design
Challenge trust assumptions before they become expensive to reverse.
Each targets a different layer of the system. Find yours below, or tell us the scope and a principal will point you to the right review.
What we review
Choose the closest review target. If your scope crosses categories, we can combine the relevant expertise into one engagement.
Timing
Challenge trust assumptions before they become expensive to reverse.
Review the system once its behavior and critical paths are stable enough to test.
Reassess after an upgrade, a migration, or a change to who holds the keys.
Reconstruct failure paths and identify the changes needed to prevent recurrence.
Our approach
Identify the system or change to review. Agree the boundaries, exclusions, and evidence needed for your decision.
Document the actors, assets, trust assumptions, and failure scenarios relevant to the scope.
Assign specialists for the system under review. Examine the controls and document findings with supporting evidence.
We always verify fixes through retesting and record unresolved findings. Deliver the agreed outputs with conclusions tied to the reviewed scope.
Your review team
A principal leads each engagement. Your proposal names the specialists assigned to the scope.
Founder & Partner
Led a security engineering practice for Rust and non-EVM systems across Substrate and NEAR. Earlier, built vulnerability-detection engines at Invicti used by Fortune 50 and public-sector organizations.
Principal Advisor
Head of Security at Agora, responsible for security, data protection, and corporate IT risk. Earlier at EY, led assessments across financial services, healthcare, and government.
Specialist Advisor
Offensive security specialist with 10+ years of experience, 100+ public audits across 8+ ecosystems, and OSCP, OSCE, eWPT, and eWPTX certifications. At ING and Binance, worked across red teaming, exploit development, infrastructure, and high-scale digital asset systems.
Published reports
Each report includes the full findings and severity ratings.
NEAR Intents Security Review
Medium Potential Funds Stealing From Users Via Repeating Failed Intents
Web Application Security Review
Critical Vulnerable to React2Shell
Pallet Pass Security Review
High DoS of The Main Functionality Through Session Key Hijacking
Onchain Orderbook and Perpetual Trading Security Review
Critical Order Placement with Negative/Zero Margin Ratio Is Possible
FAQ
Yes. We always provide remediation guidance and verify fixes through retesting. The final report records the remediation status and any unresolved findings.
Start with the system or change you want assessed. A principal helps identify the relevant code, infrastructure, cryptography, or operational scope. Work spanning several areas can be combined in one engagement.
Describe the system, your main concerns, and your deadline. Share architecture documentation and details of the environment. For any review that includes code, we need access to that code to define the scope and estimate the work. We agree how to exchange confidential material during scoping.
The scope, technical complexity, available documentation, and depth of testing determine the effort. Access requirements and the included retesting also affect the schedule. The proposal sets out the scope, timing, and fee.
Your proposal names the principal and specialists assigned to the engagement. A principal stays involved from scoping through delivery.
Describe your system, main concern, and deadline. We will help define the scope.
Discuss your scope