Home / Services / dApp penetration testing

Web3 & Crypto · dApp penetration testing

Audited contracts, compromised front-end, stolen funds.

Users never interact with your contracts directly. They interact with a website, an API and a wallet prompt — and that is where drainers, phishing kits and supply-chain attacks strike. We test the whole path from click to signature.

What we test

  • Front-end security: XSS, dependency and build-pipeline compromise, DNS and hosting
  • Wallet interaction: transaction construction, signature requests, permit and approval abuse
  • API and backend testing: authentication, authorisation, rate limiting, injection
  • Off-chain components: relayers, indexers, notification and webhook endpoints
  • Web3 libraries and RPC usage: chain-ID handling, replay and spoofing
  • Session, account and KYC flows where present
  • Phishing resilience: what a cloned site can and cannot make your users sign

What you get

  • Findings with proof-of-concept and user-impact rating
  • Remediation guidance for front-end, API and infrastructure teams
  • Content-security, dependency and deployment hardening checklist
  • Executive summary and a retest when fixes are deployed

Who it is for

Any project with a user-facing dApp: DEX and lending front-ends, NFT marketplaces, wallets, bridges, launchpads and portfolio tools. Especially relevant before a token launch or a major campaign that will draw attacker attention.

Engagement

How an engagement runs

01

Scope

We agree targets, rules of engagement and what success looks like — in writing, before anything starts.

02

Recon

We map your full attack surface the way an adversary would, not just the assets you remembered to mention.

03

Exploit

We attempt real exploitation and chain small weaknesses into business-level impact.

04

Report

You get prioritised findings, proof-of-concept and remediation steps a developer can act on today.

05

Retest

We verify every fix so issues stay closed — and you get a clean report to show customers.

FAQ

Questions about dApp penetration testing

Is this different from a normal web pentest?

The web part is similar; the difference is the wallet layer. We test what your interface asks users to sign, how approvals are scoped, and how a compromised front-end or dependency could redirect a signature — things a generic pentest does not cover.

Do you test on mainnet?

Front-end and API testing is non-destructive and can run against production with agreed rules. Anything that would move funds is reproduced on a fork or testnet.

Find out what an attacker would find first.

Send us what you want tested. We'll come back with scope, timing and a fixed quote — no sales theatre.

Start on Telegram