← Breach analysis by the Dual Vulnerabilities framework

Qantas contact centre data breach (Scattered Lapsus$ Hunters, 2025)

2025 · Australia · H - Transport and storage · Customer data theft via vishing of third-party contact centre

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Customer data theft via vishing of third-party contact centre

Dual vulnerability type

No DV evidenced

Alternative: Strategy to Execution

Why this classification

(1) The doctrinal expectation at the victim was clear and operationalised: as Australia's flag carrier holding roughly 5.67 million customer records on a CRM platform used by an outsourced overseas contact centre, Qantas was accountable under the Privacy Act for protecting that information and for its provider's compliance, and the OAIC's report documents that this doctrine was carried into practice - cyclical supplier security audits including a 2025 onsite assessment, mandatory tracked cyber-awareness and privacy training for agents, role-based access controls limiting agents to the data their role needed, contractual ISO 27001:2013 and Privacy Act/GDPR clauses, and a documented retention and scheduled-deletion regime. (2) In practice, on 28 June 2025 a threat actor posing as Qantas IT help talked an agent through a fake support-ticket closure, inducing the agent to connect their own CRM session to the actor's data extraction tool; the actor exfiltrated data across roughly two days until Qantas staff spotted unusual login alerts on 30 June, froze and revoked the account the same day, disclosed on 2 July and specifically notified all impacted customers from 9 July, with no operational disruption. (3) This is a confirmed negative case rather than a knowing-doing or doctrinal-material gap: the OAIC's preliminary inquiries ran nearly a year with access to Qantas' internal documents and concluded they did not reveal any omissions or failings in Qantas' protective steps or third-party oversight, that the enabling vulnerability was a CRM vendor default configuration that allowed an end user to authorise a third-party application connection - which the report states Qantas' role-based access controls would not have prevented and which the vendor has since changed for all customers - and that standard training would likely not have stopped the attack, so there was no gap, deferred need or unexecuted policy to classify; under the method's decision rule a formal regulator finding of no failings is the positive evidence of alignment 'No DV evidenced' requires, and no primary source documents a specific gap the regulator did not examine (its inquiry covered training, access control, third-party management, detection, containment, notification and data retention). The entry mechanism is documented and the response timeline is documented, but neither evidences a victim-side gap; the actor's attribution is expert-based and claimed, not official, and is not load-bearing. Risk markers RM13 and RM45 record the trust boundary and process design through which the incident arrived, without a DV lens sentence, as the DV-Type is No DV evidenced.

Risk markers

Sources

Notes

Data quality: the case file spells the victim 'Quantas'; the incident and source_url (ABC, 2 July 2025) identify Qantas Airways Limited. The row description (nearly 6 million customers, 'significant' proportion stolen) matches the ABC article. Timeline: incident 28 June 2025, detected and contained 30 June, public disclosure 2 July, confirmed total ~5.7 million customers (ABC, 9 July 2025; OAIC: ~5.67 million records incl. overseas, ~5.12 million Australians). Actor: CyberCX and threat-intelligence firms saw Scattered Spider hallmarks; the collective Scattered Lapsus$ Hunters claimed the attack and on 11 October 2025 published the data (reported ~153 GB) after its ransom deadline passed (The Guardian, 13 October 2025); Qantas said the nature of the compromised data had not changed since July. The October extortion wave was reported as a broader campaign against Salesforce customers; the row describes the June contact-centre incident and is classified on that. The OAIC report reflects preliminary inquiries only, states it does not make concluded findings and is not an endorsement, and individual and representative complaints (incl. a Maurice Blackburn representative complaint, July 2025) remain open; a commentary piece (Michael West Media, Sept 2025) argued the attack pattern was foreseeable from Salesforce/Google warnings, but that is opinion, not a primary source documenting a gap the regulator did not consider. DV-Type follows the method-spec decision rule on a regulator finding of no failings (first applied to this row's OAIC report). Link check: qantasnewsroom.com.au was unreachable at check time (timeout); the page was opened and read during research.