Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    A Shopify Chargeback App Exposed 200,000+ Merchant Records - After Allegedly Rejecting a Bug Bounty Report

    A vulnerability in the Disputifier chargeback app let an attacker issue over $2m in unauthorised refunds and exposed data for 200,000+ stores. Here's what happened and how to vet apps like it.

    A Shopify Chargeback App Exposed 200,000+ Merchant Records - After Allegedly Rejecting a Bug Bounty Report

    On 9 January 2026, a vulnerability in Disputifier, a Shopify app used for automated chargeback and dispute management, was exploited by an attacker who issued more than $2 million in unauthorised refunds across affected stores. The same flaw reportedly left data belonging to more than 200,000 stores exposed, including store names, Shopify URLs, owner details, email addresses, phone numbers, business addresses, API tokens and payment processor credentials. A security researcher operating under the handle @BagAnnihilator ("Serb") disclosed the issue publicly, saying Disputifier had previously declined to engage with a responsible-disclosure bug bounty report covering the same flaw, a characterisation that comes from the researcher's own account rather than anything Disputifier itself has confirmed, so we're presenting it as an allegation, not an established fact.

    What's confirmed, and what's still the researcher's account

    The scale of the incident (the $2m+ in unauthorised refunds, the 200,000-plus affected stores, and the specific categories of exposed data) is consistent across multiple independent reports we reviewed. What we'd treat more cautiously is the exact sequence and motive behind the bug bounty rejection: that detail comes from the disclosing researcher, and we haven't found independent corroboration of it from Disputifier or a third party present during that exchange. We're including it because it's a central part of how this story has been reported, not because we can verify it ourselves.

    Disputifier's own response, per the same reporting: the company disabled refunds, reversed the majority of the fraudulent transactions, pledged full reimbursement to affected merchants, and said it was cooperating with law enforcement. The app is no longer available for new installs.

    Why chargeback apps are a particularly sensitive category

    A dispute-management app needs broad access almost by definition: order history, customer PII, and often payment processor credentials, so it can act on a merchant's behalf when a chargeback comes in. That's a wider blast radius than, say, a product-options app, and it's exactly the category of app where a single flaw can expose the most consequential data a store holds, rather than just cosmetic storefront content.

    A practical app-vetting checklist

    Whether or not every detail of this specific incident gets fully resolved publicly, the underlying lesson holds regardless:

    • Review requested OAuth scopes before installing anything that touches orders, customers or payment data: ask whether the access requested actually matches what the app needs to do its job.
    • Check a vendor's security disclosure history where you can find it. How a company has handled previous reports is a reasonable proxy for how it'll handle the next one.
    • Prefer apps with a public bug bounty programme. It's not a guarantee of security, but it's a signal the vendor has at least built a process for researchers to report problems safely.
    • Audit installed apps on a quarterly schedule, not just at install time. Permissions and risk profiles change as apps get updated, and a review that only happens once is a review that goes stale.

    This sits alongside October's Shopify checkout hijack incident as a second, quite different example of the same underlying risk category this year: a trusted third-party app, sitting on sensitive data or storefront access, becoming the actual point of failure rather than Shopify's own platform.

    FAQ

    How do I check what data a Shopify app can access before installing it? Review the OAuth permission screen shown at install time carefully: it lists exactly what the app is requesting access to, and treat any request that seems broader than the app's stated purpose as a reason to look closer before proceeding.

    What should I do if I was using the affected app? Based on the reporting available, Disputifier disabled refunds and pledged reimbursement for affected merchants. If you used the app, that's worth following up on directly with the vendor, alongside rotating any API tokens or credentials you had connected to it as a precaution.

    If you'd like your current Shopify app stack reviewed for this kind of exposure before it becomes a problem, Deploy can run that audit as part of our wider security work.

    Sources: Cyber Kendra's original report, abZ Global's writeup on the Disputifier incident, Glinteco's security alert. Some details of this incident, particularly around the alleged bug bounty rejection, rely on the disclosing researcher's own account and haven't been independently verified by us.

    Last updated 20 January 2026.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.