Oz Hair and Beauty breach: scope and customer checks
- scam alert
- data breach
- oz-hair-and-beauty
- au
Correction - 4 November 2026. The earlier version described a possible breach without linking the company statement, implied an incident-specific scam wave and gave a blanket password-reset instruction. This version attributes the confirmed scope and distinguishes it from general precautions. The original publication date, 20 August 2026, is retained.
What the company says
Oz Hair and Beauty's official statement says an unauthorised third party briefly accessed its online purchase and order platform. The company says limited personal information of some customers was accessed and that it implemented containment measures and began a forensic investigation.
Its FAQ identifies information associated with purchases before August 2026: names, contact details and purchase data. The company says credit-card details, passwords, payment information and invoice details were not involved. Those exclusions matter when deciding what the report does, and does not, say about your accounts.
The statement also says affected customers are being contacted directly by email. Its FAQ gives a 22 August 2026 notification cutoff qualified by the investigation's findings at that time. These are the company's statements about its investigation, rather than a guarantee covering every person's later circumstances.
How to use the notice
Read any verified notification for the information relevant to you. Compare its description with the official notice and ask the company for clarification through independently obtained details if the scope is unclear. The fact that you once purchased something does not, by itself, identify which fields were affected.
The statement does not provide a visible publication date on the page cited here. This correction therefore does not assign it a precise first-publication time or claim that this page's original date marks the discovery of the incident.
It also does not establish an attacker identity, a customer count or an actual follow-up scam campaign. An allegation from a third party and a finding attributed to the company should remain separate. Sharing a large number from a headline without its source can turn an unresolved claim into an apparent fact.
Questions to ask about a purchase-related message
Purchase details can make a message feel familiar. Familiarity is still insufficient to establish who sent it. The NCSC's phishing guidance recommends verifying doubtful contact through details obtained from the organisation's official website.
An illustrative example is a text offering a refund for an old order but asking for a new card payment first. This page has not confirmed such a text in this incident. Before responding, check the order through the retailer's normal account or support channel. Ask what the proposed refund relates to and how the request can be confirmed against the purchase.
Treat a request for a password, one-time security code or remote access as a reason to pause. Do not supply additional information solely because the sender correctly quotes your name or a past purchase. Equally, the presence of a link alone is not a complete test of whether a communication is genuine; check its context and verify important requests independently.
The scam checker can provide an additional check on a suspicious message. It does not confirm whether your personal information was included in this breach.
Match your response to what happened
The company's statement does not establish that passwords were exposed. General advice to use unique passwords should not be presented as evidence that this incident requires every customer to reset an account. Follow verified instructions for your own account and act on signs of compromise.
If you entered a password on a suspicious page, change it through the genuine service and change reused copies. If you disclosed banking details or made an unexpected payment, contact your bank. If you installed software or used a work device at the sender's direction, tell the relevant support or IT team what happened.
Keep the message and a short account of the action you took. Avoid putting passwords, security codes or full payment details in a public report. The NCSC recovery guide and our damage-control checklist offer ways to organise the response.
Reporting suspicious contact in Australia
Use Scamwatch for a scam report and ReportCyber for cybercrime. Describe the actual approach and any loss, rather than assuming it came from the same people involved in the retailer's incident. Verify customer-specific questions directly with the retailer.