Coles is investigating a cyber security incident, but an investigation is not the same as confirmation that every customer’s information has been stolen. The useful response starts by separating the company’s dated statement, anything unusual in your own accounts, and messages from people claiming they can help.
In its 16 November 2026 ASX announcement, Coles said its investigation had not identified evidence that customer, team or supplier data had been compromised or removed. It said stores and online shopping continued operating and that it was working with the Australian Cyber Security Centre and external specialists. Those are the company’s reported findings at that stage, not an independent forensic conclusion by this publication.
This guide was researched on 18 November. It offers a practical way to organise a customer response without turning uncertainty into either panic or a guarantee. It does not identify an attacker, establish a technical cause, promise compensation or claim that a reader’s individual account has been inspected.
Read the date and the qualification together
The words “investigation to date” matter. They describe the scope of a current finding and leave room for later evidence. Removing that qualification produces two misleading extremes: “all customer data was stolen” and “there was definitely no exposure.” Neither follows from the statement used here.
Save the date of an announcement beside its main finding. If a later notice changes the position, retain both dates rather than silently replacing the old wording in a screenshot. This helps distinguish a genuine update from two people quoting different stages of an investigation. It also avoids treating the day you discovered a report as the day the event occurred.
A retailer’s ability to process orders is another separate question. Operational availability does not, by itself, settle what happened to information. Equally, a problem completing one order does not establish that a customer’s data has been stolen. Describe the observation you actually have before attaching a cause to it.
Use the company’s update page as your reference point
Coles maintains an incident update and customer FAQ page. At retrieval, its statement was labelled current as at 16 November, 8:30 a.m. The FAQs said there was no indication of Flybuys impact, no identified issues with the named subscription services, and that Coles gift cards continued working under their usual terms. It directed customers with concerns to its customer response team.
The same page says Coles will not request passwords or sensitive account information through unsolicited email or SMS. That is a useful distinction when a new message arrives. A notice pointing you toward a public update is different from a message demanding that you disclose a password to “secure” an account.
Open the known website yourself when checking developments. The Australian Cyber Security Centre’s browsing guidance recommends carefully entering a known address rather than relying on a lookalike site. Treat a search result or a forwarded link as a route that still needs checking, especially before entering personal information.
Decide which situation actually describes you
An incident headline, a suspicious message and an unauthorised transaction call for different next steps. Write down which one you have observed. It is possible to be concerned by the news without having evidence of a problem in your own account, and it is possible to have an urgent account problem whose connection to the news is unknown.
If you have only seen the headline, read the official notice and review your normal account-security habits. If an unexpected message has arrived, verify it through a separately obtained contact route before responding. If money has moved without your approval or banking credentials have been disclosed, the priority is contacting the financial provider promptly rather than waiting for the retailer’s investigation to finish.
Scamwatch’s response guidance advises contacting the bank or card provider immediately after a scam and asking them to stop transactions. That does not guarantee a refund or establish which organisation caused a loss. It gives the provider an opportunity to assess the specific payment and available protective action.
Build a short account of what you observed
The OAIC’s guide to responding to a breach notification recommends keeping a record of actions and assistance. It also explains that a notification should identify the kind of information involved and suggest a response. You can use those principles to make a clear note before contacting support.
Keep five fields: the date and time, the account or service involved, the observation, the action already taken, and the reference supplied by support. “The order page showed an unfamiliar delivery address” is more useful than “everything has been hacked.” The first statement gives someone a specific event to examine; the second combines an observation with a conclusion you may not be able to establish.
For an original fictional example, imagine Mira notices an unfamiliar order while checking her account. Her note records the order reference, when she first saw it, whether she recognises the destination, and the time she contacted the retailer. She does not invent the time the order was created if the screen does not show it. Unknown information stays marked unknown.
Keep this note private. When sharing a screenshot in a public discussion, remove account identifiers, addresses, barcodes, card details and any other information another person could use. A public warning does not need to include the evidence package intended for the organisation investigating your case.
Strengthen passwords through the account itself
The ACSC’s password guidance recommends unique, unpredictable passwords of suitable length and changing passwords believed to be compromised. Where a password is used, it recommends at least 15 characters while meeting the service’s requirements. A password manager can help maintain different credentials for different accounts.
Do any change through the genuine app or website you opened independently. A message offering a convenient reset button may be the very thing that needs verification. A new password also should not be an obvious variation of the old one or a credential already used for email, banking or another shopping account.
Consider a fictional household that uses one password for three services. Replacing it on only one service does not make the other two credentials unique. The practical job is to identify the reuse and give each account its own credential. This is a prevention example; it is not evidence that Coles passwords were exposed in this incident.
Add verification without handing it to a caller
The ACSC’s multi-factor authentication guidance recommends enabling additional verification for important accounts, including email, banking, shopping and government services where available. Options vary by provider, so follow the settings and recovery instructions of each service. Do not assume that every shopping account offers the same features.
An authentication code belongs in the process you intentionally started on the genuine service. It is not a receipt to read out to an unexpected caller. If someone tells you that sharing a code will cancel a fraudulent purchase, stop and verify the request through the organisation’s published contact route. The caller’s description of what a code does is not proof.
The distinction is especially useful when helping a family member. You can sit beside them and explain the next screen while allowing them to enter their own credentials. Taking copies of their passwords or recovery codes creates a separate information-handling problem and is unnecessary for simply reading instructions together.
A familiar sender label does not settle authenticity
ACMA’s phone and SMS guidance warns that scammers can disguise numbers, copy logos and place messages in the same conversation chain as genuine communications. It recommends independently finding information through the website or app, withholding sensitive information from unverified contacts and refusing unsolicited remote access to a computer.
That makes the requested action more informative than the message’s appearance. Is it asking you to provide a secret, install software, move money, or act before you can check? Those demands deserve examination even when the message uses a familiar business name and refers to a real incident.
A fictional text might say an account will close in ten minutes unless its owner verifies a password. The countdown is part of the claim, not an instruction the reader must obey. Open the established account route and look for a corresponding notice or contact support separately. There is no need to test the suspicious link to prove that it is suspicious.
Keep reward offers and receipt apps out of the response
Coles’ scam-warning page describes impersonation attempts involving rewards, gift-card offers and sponsored search advertisements. An offer of compensation or a prize should not become credible merely because customers are already discussing a security incident. Check any offer against the company’s own information before supplying details or sharing it with others.
Separately, Coles’ online-safety guidance warns about unauthorised third-party apps asking for Coles login details to produce digital receipts. It advises customers who have supplied those credentials to update the password and contact customer care. This is standing account-safety guidance, not a finding about the cause of the November incident.
Do not combine these two points into a claim that a particular reward message or receipt app caused the event. The reason to mention them is practical: a hurried attempt to check or repair an account should not involve handing the same account credentials to an unverified intermediary.
Match the response to the information involved
A later personalised notification may identify a particular category of information. Read that category carefully. Contact details, a password and an identity-document number create different questions. The OAIC advises seeking clarification from the organisation where the notice leaves questions unanswered, and contacting the financial institution through its published details for unresolved concerns involving financial information.
ID Support NSW’s guidance similarly focuses on understanding what information may be involved, protecting affected accounts, checking recovery settings and watching for unfamiliar activity. It identifies stolen money, compromised banking credentials and identity misuse as situations requiring prompt assistance. NSW residents can use its support route; people elsewhere should use services applicable to their location.
For a fictional comparison, one person receives a general incident email with no account-specific finding. Another receives a verified notification naming a disclosed document number. Giving both people an identical checklist of cancellations would ignore the difference in evidence. The useful question for the organisation is what information is involved in this person’s case and what action it recommends for that information.
Make a support conversation concrete
Before contacting the appropriate team, prepare a brief description in ordinary language. For example: “I saw this order at this time, I do not recognise it, and I have already changed my account password through the official website.” Include only details relevant to the question and supply sensitive evidence through the organisation’s verified channel when needed.
Ask what the reference number covers, whether further information is needed, and how the next update will arrive. Write down any promised follow-up rather than relying on memory. If the explanation remains unclear, ask for the next practical step. You do not need to diagnose the company’s systems to report something unusual in your own account.
Avoid opening several conflicting versions of the same story. A single chronology makes it easier to correct an error: if you later recognise a transaction, add that discovery with its date. Preserving the correction is more useful than continuing to repeat an earlier suspicion as a confirmed loss.
Be careful with offers to recover money
Scamwatch warns that people who have lost money can be targeted again by someone offering recovery. Its guidance points to IDCARE for free identity and cyber-support planning, and to reporting channels after protective steps have been taken. A report can contribute information and help identify the appropriate response; it is not a promise that funds will be returned.
A fictional recovery message might know the retailer’s name and offer to release a refund after an upfront payment. Knowing a public news story does not establish a relationship with the retailer or the bank. Do not allow the urgency of the original concern to become a reason to trust a second unverified contact.
If you are supporting someone else, keep the conversation practical and non-judgemental. Help them assemble their records and reach the right organisation. Blame makes it harder to discuss what was shared, while a clear account of what happened is what the next person helping them needs.
What to retain after today’s check
Keep the official update link, your private chronology and any case reference. Separate completed actions from unanswered questions. A password changed, a transaction reported and an investigation still open can all be true at once; none should be used as shorthand for the others.
For a broader message-checking walkthrough, see our suspicious-email guide. This article’s narrower purpose is to connect the dated Coles announcement with a proportionate customer response. Follow later official updates for changes to the investigation, and act on concrete account problems without guessing their cause.
Sources consulted 18 November 2026. Google Trends Australia showed “supermarket” third by search volume in the past 24 hours, at 20K+ and Active, retrieved 06:09:09 UTC. GTA VI was already covered today; the intervening cricket topic lacked a usable full current scorecard and its available explanatory angle overlapped existing coverage. The original illustration is conceptual, not a Coles interface or evidence of an intrusion.
