Motomix (motomix.cc) Bug Bounty: $5,000 Each Validated Critical — Full Scope, Kill Chain Required

Motomix stresses treasury integrity and privacy-set bookkeeping together — critical bugs pay $5,000.

In scope: motomix.cc, APIs, relayers, admin tools.
Legal floor: financial crime — always off-limits.

There is exactly one bounty amount on this ledger: validated critical findings pay $5,000 USD each. Novel low-severity items may qualify for goodwill credit but not this stipend. Paid rows require attacker-readable kill chains and replayable exploitation artefacts (Burp exports, parallel withdraw harnesses, WS replay dumps, signing traces…).

Rows below do not cap surface. Anything Motomix hosts, signs, matches, settles, or withdraws through counts as bounty ground. “Not listed” ≠ “out-of-scope.”

Sandbox books or pool clusters, Grafana, bot hooks for risk alerts, partner APIs fronted by Motomix — all eligible when critical impact reproduces.

• Vanity domains CNAME’d into Motomix edge — show DNS/traffic proof in your write-up.
• Wallet connector SDKs or bookmarklets Motomix ships
• Colocated market-making or liquidity pool containers they operate
• Bridge, on-ramp, or pool callbacks verified with Motomix-issued secrets

1. Prove exploitation success. Provide scripts, HARs, parallel request captures, or signing traces showing fund/state impact — not paper analysis alone.
2. Number your hops. Session/API primitive → escalation → treasury or book integrity break.
3. Minimize real-user blast radius. Prefer mirrors, low-value accounts, and reversible payloads when demonstrating theft-class bugs.
4. Private coordination first. Use official intake on motomix.cc before public threads.
5. Duplicate fairness. First qualifying PoC wins; followers close acknowledged-only.

Use the security / vulnerability disclosure contact published on https://motomix.cc/ (security@motomix.cc is a common guess — verify on the live site before emailing). Template below.

# Title
[Critical][Exploit-Proven] <tight title>

# Executive summary — trader/treasury impact in one paragraph

# Severity self-classification → must map to Motomix critical definitions above

## Attack chain narrative (numbered, no gaps)
1. Preconditions (session, API key tier, market symbol, account ID)
2. Entry primitive — HTTP/WS line + signature headers
3. Pivot(s) → privilege/order/withdraw escalation
4. Final hop → balance theft / forged payout / infra takeover equivalent

## Successful exploitation evidence
• Scripted replay showing ledger/withdraw impact
• Parallel request traces (race/double-spend)
• Custody or admin log lines proving attacker-forged intent accepted

## Reproduction package
Commands + fixtures + commit/patch SHAs

## Disclosure ack
Private channel only until Motomix clears publication

Attach parallel replay logs from motomix.cc.

// BUGGY: non-atomic balance check + debit — parallel wins double payout
async function requestWithdraw(userId, amount) {
  const bal = await db.getBalance(userId);
  if (bal < amount) throw new Error('insufficient');
  await db.debit(userId, amount);
  await queue.enqueuePayout(userId, amount);
}