Visa Loyalty Program Data Leaked in Third-Party Vendor Breach

Visa Confirms Third-Party Breach by 'n0n' Gang; Premium Data Leaked

HIGH
November 19, 2026
6m read
Data BreachSupply Chain AttackThreat Actor

Impact Scope

People Affected

6000+

Industries Affected

FinanceHospitality

Geographic Impact

Asia-Pacific (regional)

Related Entities

Threat Actors

n0n

Other

Visa JPMorgan ChaseExpedia

Full Report

Executive Summary

Visa has acknowledged a data security incident stemming from a compromise at an unnamed third-party service provider in the Asia-Pacific (APAC) region. The breach was claimed by the emerging extortion group n0n, which subsequently leaked a dataset allegedly containing information on over 6,000 premium Visa customers. The data appears to be related to marketing and loyalty programs, specifically Visa's luxury dining offerings. Visa has been quick to state that its core payment systems were not impacted and that no payment card numbers were exposed. However, the leaked information, which includes campaign engagement details, poses a significant risk of targeted social engineering and phishing attacks against affluent cardholders.


Threat Overview

The threat actor, n0n, a data extortion group that first surfaced in September 2026, listed Visa on its dark web leak site on November 16, 2026. The group set a 48-hour deadline for negotiation, after which it published a file named campaign_directory.csv. This file contains data related to cardholder interactions with Visa's premium loyalty and dining programs.

The breach did not impact Visa's internal networks. Instead, it was a classic supply chain attack, where attackers targeted a weaker link in the operational chainβ€”in this case, a vendor managing marketing campaigns. The leaked data includes details like campaign names, event counts, and dates. While seemingly innocuous, this information reveals personal habits, travel patterns, and interests of high-value customers, making them prime targets for follow-on attacks.


Technical Analysis

The attack was executed by the n0n extortion group, which focuses on data theft and extortion without deploying encrypting ransomware. Their modus operandi involves gaining access to a target's network (or a supplier's network), exfiltrating sensitive data, and then using the threat of public release to extort a payment.

Analysis of the leaked .csv file suggests the compromised system was likely a marketing or customer relationship management (CRM) platform used to track the performance of loyalty campaigns. The data itself is metadata about customer engagement rather than primary payment information. The attack vector used to breach the third-party vendor was not disclosed.

Analyst-Assessed MITRE ATT&CK Techniques


Impact Assessment

While Visa successfully protected its core payment infrastructure, the incident still carries significant impact. The primary risk is to the affected premium cardholders. The leaked data provides a 'goldmine' for social engineering, allowing criminals to craft highly convincing phishing emails or pretexting calls. For example, an attacker could reference a specific dining event the victim attended to build credibility before soliciting sensitive information.

This poses a reputational risk to Visa, as high-net-worth customers may lose confidence in the security of programs designed for them. It also serves as a stark reminder of the pervasive nature of supply chain risk; even with robust internal security, an organization's security posture is only as strong as its weakest vendor. For the unnamed third-party vendor, the impact is severe, likely involving loss of business, regulatory scrutiny, and legal liability.


IOCs β€” Directly from Articles

No specific Indicators of Compromise (IOCs) were mentioned in the source articles.


Cyber Observables β€” Hunting Hints

Security teams at organizations running loyalty programs should hunt for the following patterns:

Type
file_name
Value
*campaign*.csv, *loyalty*.sql, *members*.zip
Description
Search for suspicious creation or exfiltration of files with names related to marketing campaigns or customer lists.
Type
log_source
Value
Database audit logs
Description
Monitor for unusual or large-scale query activity against customer or marketing databases, especially from non-standard application service accounts.
Type
network_traffic_pattern
Value
Large data transfers from marketing servers to unknown external IPs
Description
Baseline normal traffic from marketing platforms and alert on significant deviations, which could indicate data exfiltration.
Type
url_pattern
Value
Dark web leak sites associated with extortion groups
Description
Monitor for mentions of company or brand names on known extortion leak sites.

Detection & Response

Detection

  • Third-Party Monitoring: Implement services that monitor the dark web and extortion sites for mentions of your brand, executives, and key suppliers.
  • Data Loss Prevention (DLP): Deploy DLP solutions to monitor and block unauthorized exfiltration of structured and unstructured data matching customer information formats.
  • D3FEND: Use D3-UDTA: User Data Transfer Analysis to baseline and detect anomalous transfers of sensitive user data, particularly from marketing or CRM systems to external destinations.

Response

  • Customer Notification: Proactively and transparently notify affected customers about the specific data exposed and the potential risks (e.g., targeted phishing).
  • Phishing Awareness: Launch a targeted awareness campaign for affected customers, providing clear examples of how the leaked data might be used against them.
  • Vendor Offboarding: Immediately suspend the compromised vendor's access to all systems and data and initiate a full security review of the relationship.

Mitigation

Strategic Mitigation

  • Vendor Risk Management: Implement a robust third-party risk management (TPRM) program. This must include rigorous security assessments during onboarding and continuous monitoring throughout the vendor lifecycle. Mandate that vendors handling sensitive data adhere to your organization's security standards.
  • Data Minimization: Only share the absolute minimum amount of customer data necessary for a vendor to perform its function. In this case, the vendor may not have needed specific identifiable information to track campaign engagement.
  • D3FEND: Apply the principles of D3-DTP: Domain Trust Policy to vendor relationships, establishing strict data sharing and access control policies based on a zero-trust model.

Tactical Mitigation

  • Contractual Obligations: Ensure vendor contracts include strong security clauses, breach notification requirements (e.g., within 24-48 hours), and liability for security failures.
  • Credential Security: Mandate that vendors use secure methods for accessing any of your organization's data or systems, including the use of scoped API keys and MFA, and prohibit the use of shared or long-lived credentials.

Timeline of Events

1
September 1, 2026
The 'n0n' extortion group first appears.
2
November 16, 2026
The 'n0n' group lists Visa on its dark web leak site and sets a 48-hour deadline.
3
November 19, 2026
The 'n0n' group leaks the stolen data after the deadline passes. Visa confirms the breach originated at a third-party vendor.
4
November 19, 2026
This article was published

MITRE ATT&CK Mitigations

Implementing a robust third-party risk management program that includes assessing the security posture of vendors is crucial.

Enforce the principle of least privilege, providing vendors with access only to the data and systems absolutely necessary for their function.

Affected customers must be trained to recognize sophisticated phishing attempts that may leverage their stolen personal information.

Timeline of Events

1
September 1, 2026

The 'n0n' extortion group first appears.

2
November 16, 2026

The 'n0n' group lists Visa on its dark web leak site and sets a 48-hour deadline.

3
November 19, 2026

The 'n0n' group leaks the stolen data after the deadline passes. Visa confirms the breach originated at a third-party vendor.

Article Author

Jason Gomes

Jason Gomes

β€’ Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

Visan0nData BreachSupply Chain AttackExtortionThird-Party RiskAsia-Pacific

πŸ“’ Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

πŸ›‘οΈ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

πŸ”— STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph β€” relationships between actors, malware, techniques, and indicators.

⚑ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.