Skip to main content
Emerging ThreatsData Breaches

Leaked Visa, Mastercard Data Exposes Phishing Risks

Modern data storage room with empty server racks and a laptop screen in the foreground.

"We found no card numbers, expiry dates, CVVs, passwords, dates of birth, or home addresses in any file," Ensar Seker, chief information security officer at SOCRadar, told The Register after his team parsed the data published by the extortion group n0n.

SOCRadar’s parsing: what the 14 leaked files actually held

Researchers at SOCRadar examined all 14 files that n0n published as samples from alleged thefts involving Visa and Mastercard. Their scan turned up no direct payment credentials: no full card numbers, expiry dates, CVVs, passwords, dates of birth, or home addresses, the company reported — a finding that Visa’s own statement that no card numbers were affected “matches our scan,” SOCRadar said.

Data elements that enable phishing and impersonation

Although the files lacked account-draining details, SOCRadar found information that can meaningfully assist social-engineering and phishing operations: mobile phone numbers, Bank Identification Number (BIN) prefixes, and dated airline, hotel, and restaurant bookings. SOCRadar’s CISO warned that those elements are precisely the information needed for an attacker to pose as a concierge desk or a bank by email or voice.

Scope, provenance, and the possibility of further releases

The published files represent a small fraction of what n0n claims to have taken: roughly 4.3 GB and 1.9 million marketing events, or about 0.4% of the claimed haul. SOCRadar noted that both leaked Visa and Mastercard datasets appear to come from the same upstream provider: they use an identical 27-column booking layout, the same placeholder text, and matching CRM ID formats. The most recent records in each dataset stop 69 seconds apart on October 26, which SOCRadar interpreted as looking “like two card programs run on one provider's platform” and resembling “a batch copy from a marketing and reporting store.” SOCRadar also cautioned that a further release of data remains possible.

Connection to the Qubole supply‑chain campaign and n0n’s claim

All three financial firms — Visa, Mastercard, and JPMorgan Chase — told The Register they are investigating third-party breaches that may involve customer information. The timing of the published files aligns with a supply‑chain campaign disclosed earlier in November by Wiz, working with Google's Mandiant incident responders and AI data‑security company Sentra. In that disclosure, threat hunters said the October 14 attack used compromised identity and access management (IAM) credentials associated with Qubole's AWS account to access dozens of downstream customers, exfiltrating secrets and sensitive data from S3 buckets. N0n has claimed responsibility for the thefts; SOCRadar’s assessment that the timing fits the Qubole campaign is explicitly described as its own analysis, not a confirmed finding. Qubole’s parent company, Idera, did not respond to inquiries, and the financial institutions declined to say which provider(s) were breached or whether Qubole was the access path.

How technologists, enterprises, and consumers should read the record

  • Technologists and security teams: the files’ structure — a 27-column booking layout and matching CRM IDs across datasets — points to a batch export from a marketing/reporting store supplied by a third party. Teams responsible for data pipelines and third‑party integrations should treat marketing and booking stores as sensitive repositories, not just low-risk marketing assets.
  • Affected enterprises and procurement leaders: the three financial firms attribute the incident to a third‑party provider and declined to name the vendor. That underlines the importance of visibility into downstream and supply‑chain access paths (including IAM credentials tied to vendor cloud accounts) and the need to press vendors on incident response commitments and logging of third‑party access.
  • End users and consumers: the leaked samples do not contain card numbers or other payment credentials that would directly enable account takeover or immediate financial theft, but they do contain contact and booking details that can be used to craft convincing phishing or impersonation attempts.

n0n’s public posting of sample files follows a common extortion pattern — leaking partial data ahead of an official deadline to increase pressure on victims — and the published samples amount to a small sliver of what the group claims to possess. That combination — plausible links to a supply‑chain access path, public sample data that aids impersonation, and the possibility of further releases — leaves several concrete next steps: forensic confirmation of the access path, vendor-level disclosure about which upstream provider was affected, and outreach to recipients of the exposed marketing records to warn of targeted phishing risks.

Source: The Register