hunt-fintech-graphql

Test fintech GraphQL APIs for money-movement, ledger, and authorization vulnerabilities.

1|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-fintech-graphql-marcboggs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hunt-fintech-graphql
Source: https://github.com/marcboggs/BMAD-AppSec-Orchestrator/tree/main/.claude/skills/hunt-fintech-graphql
Command: npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill hunt-fintech-graphql-marcboggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fintech GraphQL APIs sit in front of ledgers, wallets, and payment systems where a single resolver bug can move real money, yet generic GraphQL testing guidance misses the financial-specific attack surface like idempotency replay, decimal rounding abuse, and source-account authorization gaps. ## Core Features & Use Cases - Money-Movement Mutation Testing: Systematically map and probe transfer, withdrawal, redemption, and top-up mutations for non-atomic ledger writes, idempotency-key bypass, and double-spend via alias batching. - Decimal & Precision Abuse Probes: Test custom Money/Decimal scalars with sub-cent amounts, scientific notation, oversized values, and negative amounts to expose rounding drift and float-parsing fallbacks. - Fintech-Specific Authorization Checks: Detect asymmetric IDOR where source-account ownership is never validated, field-level PII leaks on nested KYC fields, and admin-tier mutations reachable via mass assignment. - Use Case: When hunting a neobank or brokerage target exposing a GraphQL endpoint, use this skill after generic schema discovery to test whether a transferFunds mutation validates that the source account belongs to the caller, and whether replaying an idempotency key produces duplicate ledger writes. ## Quick Start Ask the AI to hunt fintech-specific GraphQL vulnerabilities on an authorized banking or payments target that exposes money-movement mutations.

Frequently Asked Questions about hunt-fintech-graphql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test GraphQL transfer mutations for double-spend vulnerabilities?▼

Send the same mutation twice with an identical idempotencyKey to check server-side dedup, then use alias batching to repeat a redeem or transfer mutation multiple times in one request. If multiple aliases succeed, escalate with parallel HTTP requests to confirm a real double-spend.

What is source-account IDOR in fintech GraphQL APIs?▼

It occurs when a transferFunds-style mutation validates the destination account but never checks that the source account belongs to the authenticated caller. Test by substituting a victim account ID as the source while using your own session and an attacker-controlled destination.

How does this differ from generic GraphQL security testing?▼

Generic GraphQL testing covers introspection, IDOR, and batching mechanics, while this skill adds the fintech delta: ledger write atomicity, decimal and rounding abuse on Money scalars, idempotency enforcement, and KYC field-level authorization. Run generic discovery first, then apply this methodology.

What evidence is required to report a fintech GraphQL vulnerability?▼

You must demonstrate an actual ledger state change, such as a balance difference queried before and after the attack, not just a success response. Race-condition findings should be reproduced twice from a clean state to prove determinism.

Can decimal precision bugs in GraphQL APIs be exploited for profit?▼

Yes, when a Money or Decimal scalar falls back to native float parsing or rounds inconsistently between client and server. Probe with sub-cent amounts, scientific notation, and oversized values, then repeat small rounding discrepancies to accumulate balance drift.