Active Program $5,000 flat · validated critical Escrow · APIs · P2P · wallets · dispute · full mesh

MidMan (midman.io) Bug Bounty: $5,000 Each Validated Critical — Full Scope, Kill Chain Required

MidMan at https://www.midman.io/ operates as a dedicated crypto middleman / escrow service: trade mediation, deposit holds, release triggers, dispute arbitration, fee splitting, API-driven automation, webhook callbacks, chat and support surfaces, admin review consoles — the entire MidMan-operated perimeter is in-scope with no artificial carve-out appendix. Every confirmed critical validated with a reproducible exploitation chain pays exactly $5,000 USD. Acceptance requires both a numbered attack chain narration and evidence that the exploitation actually succeeds.

BountyHunter Editorial
May 23, 2026 ·
#MidMan #midman.io #Middleman #BugBounty
$5,000 per critical
Full scope no carve-outs
Chain + PoC kill chain · attack succeeds
01 — Overview

Middleman escrow surfaces under stress

MidMan concentrates crypto trade escrow: deposit holds, release authorization, dispute arbitration, fee accounting, chat mediation, admin overrides, and API-driven automation hooks — fertile ground for escrow theft, unauthorized release, dispute manipulation, and balance misaccounting. Each critical earns $5,000.

As a dedicated middleman platform, MidMan holds funds for every mediated trade — deposit tagging, hold ledger, release triggers, dispute overrides, fee splits — every link in that chain is a bounty-relevant attack surface. In scope materially: every host under midman.io and sibling subdomains for middleman services, API integrations, chat mediation, admin consoles, notification workers, dispute automation.
Civil exclusions only: theft-as-a-service against counterparties outside the bounty program, harassment — society-level bans.

02 — Why this matters

Why pressure-test MidMan?

Flat $5K critical payouts

Validated critical exploits with reproducible payloads earn exactly $5,000 USD.

Full-scope trust boundary

Every endpoint MidMan operates is in-scope — no carve-outs.

Real custody risk

MidMan holds escrow funds — every vulnerability that lets funds escape is a clear critical.

03 — Reward

The critical reward benchmark

$5,000USD per validated critical
  • Flat rate — no haggling over severity tags
  • Payable on kill chain + successful attack reproduction
  • Duplicate-first policies: first qualified PoC wins
  • Lower severities considered — critical bar is highest

A critical on MidMan means escrow bypass, unauthorized release of held funds, dispute outcome manipulation, mass balance disclosure, or persistent admin account takeover.

04 — Scope

What's in scope

TargetCategoryReward
midman.io, subdomains, web UIWeb$5,000 / validated bug
Escrow APIs · deposit/release endpointsBackend$5,000 / validated bug
Escrow hold ledger · release triggers · fee accountingCustody$5,000 / validated bug
Dispute arbitration · admin overridesOps$5,000 / validated bug
05 — Full Scope Policy

Everything MidMan operates — no exclusions list

Sandbox escrow environments, canary wallet clusters, Telegram/bot hooks, partner integrations — all eligible when critical impact reproduces.

  • Vanity domains CNAME'd into MidMan edge
  • Escrow SDKs or bookmarklets MidMan ships to traders
  • Bridge or on-ramp callbacks verified with MidMan-issued secrets
06 — Rules

Rules of engagement

  1. Prove exploitation success. Provide scripts, HARs, parallel request captures.
  2. Number your hops. Session/API primitive → escalation → escrow integrity break.
  3. Minimize real-user blast radius. Prefer mirrors and low-value accounts.
  4. Private coordination first. Use official intake on midman.io.
  5. Duplicate fairness. First qualifying PoC wins.
07 — Submit

How to submit a report

Use the security disclosure contact on https://www.midman.io/ (security@midman.ioverify on the live site).

  1. Summary and type of vulnerability
  2. Numbered kill chain from entry to impact
  3. Proof of successful exploitation
  4. Suggested remediation (optional)
08 — Example

Escrow release race vignette · pair with parallel request logs

Illustrative race on escrow release + dispute check — worthless without captures on midman.io.

TypeScript — Escrow Release Handler
// BUGGY: TOCTOU race — dispute check and release are not atomic
async function releaseEscrow(tradeId: string) {
  const trade = await db.getTrade(tradeId);
  if (trade.status !== 'held') throw new Error('invalid state');
  // Race window: attacker sends 20 parallel releaseEscrow() calls here
  const isDisputed = await db.hasActiveDispute(tradeId);
  if (isDisputed) throw new Error('disputed');
  await wallet.send(trade.buyerAddress, trade.amount);
  await db.updateTrade(tradeId, { status: 'released' });
}
09 — FAQ

Frequently asked questions

Is the entire midman.io domain in scope?

Yes. Any host or subdomain MidMan operates is in scope.

What qualifies as a critical?

Escrow bypass enabling unauthorized release, dispute manipulation with financial loss, or admin account takeover.

Is social engineering allowed?

No. Technical endpoint testing only.

Ready to probe MidMan's escrow surfaces?

Find a critical? $5,000 is waiting.

Start at midman.io