Skip to main content
Mallory
← Back to News
voice-social-engineeringmass-credential-exposurebreach-disclosure-notificationidentity-impersonation-fraud

Vishing Attack on Qantas Contact Center Exposed 5.7 Million Customer Records

Social Engineering & Fraud · 4 sources · Updated 4mo ago · First seen Jul 16, 2026

Vishing Attack on Qantas Contact Center Exposed 5.7 Million Customer Records

Australia's privacy regulator found that the 2025 Qantas breach affecting about 5.67 million customers began with a sophisticated tech-support vishing scam against a contact center agent. An attacker posing as Qantas IT support persuaded the employee to visit a malicious site and take actions inside the airline's CRM environment, linking the platform to a data-extraction tool and enabling the theft of customer records.

The Office of the Australian Information Commissioner said Qantas had taken reasonable steps to protect personal information and declined to pursue a formal privacy investigation or find the airline in breach of the Australian Privacy Principles. The regulator cited prior audits of the contact center, recurring privacy and security awareness training, and role-based access controls, while noting the incident depended on an uncommon social-engineering technique and a default CRM setting. Exposed data included customer names, phone numbers, email addresses, and for some individuals addresses and dates of birth; no financial data or passwords were reported compromised.

Is your org in this campaign?Get the infrastructure and lures behind it.
Hunt this campaign
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Jun 1, 2025 – Jul 16, 2026
  1. Jul 16, 20264mo ago

    OAIC declines to hold Qantas responsible after preliminary inquiry

    Australia's Office of the Australian Information Commissioner concluded its preliminary inquiry into the Qantas breach and decided not to open a formal privacy investigation or hold Qantas responsible. The regulator found Qantas had taken reasonable protective steps, including audits, training, awareness testing, and role-based access controls, and said the attack was not reasonably foreseeable or preventable through stronger existing role-based access controls alone.

    Tech support scam caused massive data breach at Australian airline Qantas
  2. Jun 1, 20251y ago

    Qantas customer data exposed in CRM breach

    In June 2025, a threat actor used a sophisticated vishing or fake IT support social-engineering attack against a Qantas contact center agent, leading to access to the airline's CRM platform and theft of customer data. The breach affected about 5.67 to 5.7 million customers and exposed details including names, phone numbers, email addresses, and for some customers, addresses and dates of birth; no financial information or passwords were compromised.

    Tech support scam caused massive data breach at Australian airline Qantas
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Qantas Airways

Breaches

1 linked
QANTASAIRWAYS-2025-06
Do you run this?Get the infrastructure, lures, and IOCs behind this campaign, ready to push into your email and identity stack.
Hunt This Campaign
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.