Executive Summary
Between October 14 and 26, 2026, the n0n ransomware group exploited compromised Qubole credentials to pivot into AWS environments belonging to J.P. Morgan Chase, Visa, and Mastercard via pre-authorized IAM roles. Qubole, a cloud data analytics platform owned by Idera, had been granted cross-account access by these financial institutions, creating a trusted supply-chain entry point. Attackers exfiltrated 53.9 GB of data directly from Qubole—including customer contracts, pricing records, and marketing data—and claimed access to nearly one petabyte of downstream customer network data. On November 16, 2026, stolen records were published on the n0n extortion site after ransom demands were ignored.
This incident underscores the accelerating risk of third-party cloud vendor abuse, where overly permissive IAM roles granted to SaaS analytics providers become silent backdoors into enterprise cloud environments. As financial sector regulators sharpen scrutiny of vendor risk management under frameworks such as PCI DSS 4.0 and DORA, the attack vector exposed here—trusted credential abuse across cloud tenants—represents one of the most difficult threats for perimeter-centric security controls to detect or contain.
Why This Matters Now
Ransomware groups are increasingly targeting cloud analytics vendors as proxy entry points into Tier-1 financial institutions, bypassing direct defenses entirely. With PCI DSS 4.0 enforcement deadlines passed and DORA now in effect across the EU, regulators expect demonstrable third-party access controls and egress monitoring. Organizations that have granted standing IAM roles to vendors without enforcing least-privilege segmentation or outbound traffic inspection face immediate and material compliance exposure.
Attack Path Analysis
The n0n ransomware group compromised Qubole credentials to gain initial access, then abused pre-configured IAM roles to assume privileged access into customer AWS environments belonging to Chase, Visa, and Mastercard. Attackers moved laterally across customer cloud tenants via trusted IAM role delegation, operated covertly over a 12-day window, and exfiltrated 53.9 GB directly from Qubole plus claimed nearly one petabyte from downstream customer networks before publishing the data on an extortion site after ransom demands were ignored.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Attackers obtained valid Qubole service credentials — likely through credential theft, phishing, or dark-web purchase — granting them authenticated access to Qubole's cloud data analytics platform. No CVE-based exploit was reported; the entry vector was compromised legitimate credentials to a trusted third-party vendor.
MITRE ATT&CK® Techniques
Valid Accounts
Valid Accounts: Cloud Accounts
Trusted Relationship
Data from Cloud Storage
Transfer Data to Cloud Account
Data Encrypted for Impact
Financial Theft
Exfiltration Over Web Service
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Third-Party Service Provider Risk Management
Control ID: Requirement 12.8
NYDFS 23 NYCRR 500 – Third-Party Service Provider Security Policy
Control ID: Section 500.11
DORA (EU) 2022/2554 – Third-Party ICT Concentration and Oversight
Control ID: Article 28 — ICT Third-Party Risk Management
CISA Zero Trust Maturity Model 2.0 – Least Privilege Access and Cross-Environment Segmentation
Control ID: Network Pillar — Micro-Segmentation / Identity Pillar — Least Privilege
NIS2 Directive (EU) 2022/2555 – Supply Chain Security and Incident Handling
Control ID: Article 21 — Cybersecurity Risk Management Measures
GLBA (Gramm-Leach-Bliley Act) — FTC Safeguards Rule 16 CFR Part 314 – Oversight of Service Provider Arrangements
Control ID: Section 314.4(f)
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Banking/Mortgage
J.P. Morgan Chase's supply-chain ransomware breach via compromised Qubole IAM credentials exposed 78 million customers' data, demanding zero trust segmentation and egress controls per PCI 4.0 and NIST 800-53.
Financial Services
Visa and Mastercard's third-party vendor compromise across 200+ countries highlights critical exfiltration risk, requiring encrypted traffic controls and east-west segmentation aligned to ZTMM and PCI 4.0 compliance mandates.
Information Technology/IT
Qubole's cloud analytics platform breach via hijacked AWS IAM roles exposes IT vendors to supply-chain ransomware, requiring multicloud visibility, zero trust segmentation, and egress policy enforcement across hybrid environments.
Capital Markets/Hedge Fund/Private Equity
n0n ransomware's exfiltration of customer contracts, pricing records, and production data via trusted vendor AWS access threatens capital markets firms relying on third-party analytics pipelines without adequate lateral movement controls.
Sources
- Vendor data breach exposes Chase, Visa, Mastercard customer infohttps://www.bleepingcomputer.com/news/security/vendor-data-breach-exposes-chase-visa-mastercard-customer-info/Verified
- Hackers exploit trusted AWS access to breach multiple cloud environmentshttps://www.bleepingcomputer.com/news/security/hackers-exploit-trusted-aws-access-to-breach-multiple-cloud-environments/Verified
- J.P. Morgan Chase announcement on third-party cyber attackhttps://x.com/jpmorgan/status/2123408240104853510Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- NVD - National Vulnerability Databasehttps://nvd.nist.gov/Verified
- Advantest confirms personal information stolen in ransomware attackhttps://www.bleepingcomputer.com/news/security/advantest-confirms-personal-information-stolen-in-ransomware-attack/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this incident because the attacker's entire kill chain depended on unconstrained cross-account reachability and unmonitored outbound data paths that Zero Trust segmentation and egress policy enforcement would likely have reduced. By enforcing workload-level segmentation and identity-aware access controls across cloud tenants, Aviatrix CNSF would likely have limited the blast radius from Qubole's environment into Chase, Visa, and Mastercard's AWS tenants.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Authenticated session activity from the compromised Qubole credentials may have been constrained to a narrowly defined network perimeter, reducing the reachability of attacker-controlled sessions into broader cloud infrastructure from the moment of initial access.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation principles applied at the workload and identity layer would likely have constrained the scope of IAM role assumption, reducing the ability of an authenticated Qubole identity to reach customer tenant resources beyond its minimum necessary access boundary.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement across cloud tenant boundaries would likely have reduced the reachability of assumed IAM role sessions, constraining lateral movement paths between Qubole's environment and each of the three downstream customer AWS tenants.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility across API-layer traffic patterns would likely have surfaced behavioral anomalies in assumed-role session activity, potentially reducing the 12-day undetected operational window by flagging unusual access volumes or timing inconsistent with normal Qubole analytics workflows.
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress policy enforcement would likely have reduced the volume of data transferable to attacker-controlled external destinations by constraining outbound data paths from both Qubole's environment and customer AWS tenants to only pre-approved egress destinations.
Had prior-stage segmentation and egress controls reduced the scope of lateral movement and data transfer, the volume and sensitivity of data reaching the extortion site would likely have been smaller, limiting downstream reputational and regulatory exposure for Chase, Visa, and Mastercard.
Impact at a Glance
Affected Business Functions
- Customer Data Management and Marketing Analytics
- Third-Party Vendor Risk and Cloud Data Pipelines
- Payment Network Cardholder Benefit Program Administration
- Digital Banking Customer Relationship Management
Estimated downtime: N/A
Estimated loss: N/A
Approximately 53.9 GB of data across 30,743 files was exfiltrated directly from Qubole systems, including customer contracts, pricing records, staff and trial-user information, and production data. The n0n ransomware group additionally claims possession of nearly one petabyte of data sourced from Qubole customer cloud environments. Confirmed exposed data categories include customer names and email addresses belonging to J.P. Morgan Chase digital banking customers (from a pool of approximately 78 million active digital users), a limited number of email addresses from Mastercard cardholders enrolled in a specific benefit program, and unspecified marketing data associated with Visa. No payment card numbers, financial account credentials, or payments processing data were confirmed as exposed. The breach originated through compromised Qubole platform credentials used to pivot into downstream AWS environments via pre-configured IAM role trust relationships between October 14 and 26, 2026.
Recommended Actions
Key Takeaways & Next Steps
- • Enforce Zero Trust Segmentation on third-party IAM roles: Apply identity-based policy and least-privilege constraints (NIST.800-53.AC-6, PCI.4.0.7.2.4) to all vendor-delegated IAM roles. Qubole's cross-account AssumeRole permissions should have been scoped to specific resources, time-bound, and subject to continuous posture validation — preventing lateral movement across Chase, Visa, and Mastercard tenants.
- • Deploy Egress Security & Policy Enforcement to block unauthorized data transfer: FQDN filtering and egress policy enforcement (NIST.CSF.PR.DS-5, PCI.4.0.3.5.1) applied at the cloud network layer would have flagged and blocked the 53.9 GB exfiltration from Qubole and the downstream bulk data staging from customer AWS environments to attacker-controlled destinations.
- • Implement Multicloud Visibility & Control to detect anomalous cross-account API activity: Centralized traffic observability and anomaly detection across the multi-cloud control plane (ZTMM.CrossCutting.Visibility, NIST.800-53.AU-6) would have surfaced the unusual pattern of a single vendor identity assuming roles across multiple Fortune 500 financial tenants over a 12-day window, enabling early incident response.
- • Apply East-West Traffic Security to constrain workload-to-workload reach within AWS environments: Microsegmentation and service-to-service flow controls (ZTMM.Network, NIST.800-53.SC-7) between Qubole's analytics workloads and customer data stores would have restricted the blast radius of the compromised vendor credential, limiting access to only pre-approved, monitored data paths.
- • Enforce Encrypted Traffic controls and audit unencrypted data-in-transit paths: High-performance encryption (MACsec/IPsec) for data in transit between vendor and customer environments (PCI.4.0.4.2.1, NIST.CSF.PR.DS-2) combined with inline IPS signature inspection on egress flows would have provided both a detection layer and a last-line-of-defense barrier against bulk plaintext data exfiltration across cloud boundaries.



