Crypto exchange penetration testing that follows a withdrawal from the button to the chain. Guardian attacks the web apps, trading APIs, admin tools and cloud, and the hot wallet systems behind them, the way an attacker after customer funds would.
Every path from a customer balance to your hot wallet.
Withdrawals Allowlists and cooldowns on new addresses, limits and 2FA enforced on the server, and parallel withdrawals raced against one balance.
Deposits and crediting Each deposit credited once, after the required confirmations, with chain watchers and webhooks that cannot be faked or replayed.
Trading APIs REST and WebSocket order routes, API key permissions and revocation, rate limits per key, and signed requests that cannot be replayed.
Matching and risk engines Order handling, liquidations, and what happens when a stream stalls, a job fails or two workers race.
KYC flows Whether KYC-gated actions check status on the server, other users’ documents by ID, file uploads, and forged vendor callbacks.
Admin and back office Every support and admin role, step-up checks before actions that move funds, and what a support login can see or change.
Hot wallet infrastructure Which cloud roles, CI runners and services can reach a signer, who approves a payout, and where policy rules apply.
Listing pipelines How a new asset or network goes live: contract addresses, decimals, confirmation counts and node setup, and who can change them.
Scoped from what the exchange does: its roles, flows and wallet tiers. Web and mobile apps, APIs and cloud can be tested together or alone, and source access is strongly recommended so nothing user-reachable is missed.
Roles, environments, wallet tiers and mainnet limits, agreed in writing before work begins.
02
Test
Every flow at every privilege level, by hand and fuzzed: balance races, tampered and replayed requests, and paths from the cloud toward a signer.
03
Fix and retest
Guardian walks your engineers through each finding, then retests the fixes.
04
Report
Scope, test window and build tested, each finding reproduced with steps and evidence, severity by what it reaches, and the retest result.
The report is evidence for your board, your bank partners and often a regulator. The executive summary example shows what leadership should take from it.
Public findings
What Guardian has found in trading backends.
Each card links a finding in a public Guardian report on a trading backend: Synthetix’s perpetual futures exchange, Ethereal’s order book and Longshot’s prediction market app.
H-06Synthetix Withdrawal Flow · High
When a withdrawal failed to submit, for example during an RPC outage, the handler still acknowledged it. The request was discarded while the user’s pending amount stayed locked, with no retry path.
A pentest report is often the evidence an auditor, bank partner or regulator asks for. Each framework sets its own scope and frequency. This covers the technical side only; confirm how each rule applies to you with counsel.
SOC 2
The Trust Services Criteria do not mandate a pentest, but a CC4.1 point of focus names one, and customers often ask for it. If your controls promise a test, run it inside the Type 2 period.
A MiCA application describes a third-party cybersecurity audit if one is available, ideally with pentests. Once authorized, MiCA sends CASPs to DORA for their ICT rules. DORA requires CASPs other than microenterprises to test the systems behind critical or important functions at least yearly, and lists pentesting among the tests.
New York’s 23 NYCRR 200.16 requires each virtual currency licensee to pentest its systems at least annually, with vulnerability assessments at least quarterly.
“Having Guardian as a strategic partner has allowed us to move more quickly while keeping security as our highest priority.”
CoinflipcanadaGMX
Questions
Crypto exchange pentest questions
What does a crypto exchange pentest cover?
Withdrawals and deposits, trading APIs, matching and risk engines, KYC, admin and back office tools, hot wallet infrastructure and listing pipelines, across your web and mobile apps, APIs and cloud.
How often should a crypto exchange be pentested?
At least annually, and after major changes. New York requires each virtual currency licensee to pentest at least annually, and DORA requires yearly testing of the systems behind critical or important functions.
Will testing touch customer funds or production keys?
Only within limits you agree first. The rules of engagement set limits on mainnet transactions, production keys, hot wallets and signer devices, and Guardian recommends testnets over mainnet where the system allows it.
Can Guardian test our contracts and backend together?
Yes. Book a smart contract audit alongside the pentest. On Avantis V2, Guardian reviewed the backend and the contracts at the same time, and several findings could only be judged with both halves in view.
Who does the testing?
Guardian’s offchain team, led by Carlos Polop, who co-founded and built HackTricks. On the Avantis exchange backend, two independent teams returned 68 findings, two of them Critical, both fixed while the review was still running.