TryBugHunt

The Double-Dipping Refund Exploit

Hardjavascript

Cumulative Balance Cap Enforcement & Idempotency Error State Machine

0:00
Step 1: Test Traffic & Expose Flaw
/**
 * Refund API Controller
 * Orchestrates ledger mutations and external payment gateway calls.
 */

class RefundController {
  constructor(ledger, gateway) {
    this.ledger = ledger;
    this.gateway = gateway;
    this.idempotencyStore = new Map();
  }

  async processRefund(request) {
    const { chargeId, amountCents, idempotencyKey } = request;

    if (this.idempotencyStore.has(idempotencyKey)) {
      return this.idempotencyStore.get(idempotencyKey);
    }

    const ledgerResult = this.ledger.recordRefund(chargeId, amountCents);

    // AI Attempt: Call external payment gateway
    // BUG: Dispatches gateway refund even if ledger rejected the amount!
    const gatewayRes = await this.gateway.executeGatewayRefund(chargeId, amountCents);

    const response = {
      chargeId,
      refundedAmount: amountCents,
      status: "PROCESSED",
      gatewayTxn: gatewayRes.transactionId,
      remainingBalance: ledgerResult.remainingCents,
    };

    this.idempotencyStore.set(idempotencyKey, response);
    return response;
  }
}

module.exports = { RefundController };
Step 1: Test Traffic & Expose Flaw

Simulate multiple partial refund requests on a single charge. Prove that customers can extract more refund money than the original charge total.

Choose Traffic Scenario to TestClick to simulate
Architectural Guide & Interview Notes
↑ Jump to Interactive Studio

Deep Dive: The Double-Dipping Refund Exploit

An engineering analysis of why this AI-generated Pull Request passed isolated unit tests, how multi-tenant traffic exposes the architectural flaw, and how interviewers score your response.

The Root Cause Anti-Pattern

The Interviewer's Scoring Rubric

Candidates are assessed on whether they jump to trial-and-error editing or follow a hypothesis-driven approach. A "Strong Hire" candidate restates the data flow between modules, explains why single-client unit tests passed, crafts an adversarial probe showing cross-tenant leakage, and implements a surgical 1-line patch without breaking existing contracts.

Candidate Strategy for the Code Comprehension Round

  1. 1Map Module ContractsTrace how the gateway invokes the underlying service. Note what data is passed by reference vs. by value.
  2. 2Break It With An Adversarial ProbeSimulate concurrent or sequential traffic across multiple identities to force shared state mutation.
  3. 3Deliver a Surgical PatchMake the minimal required diff to ensure proper per-client state isolation without refactoring unnecessary files.