Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Coles cyber attack: what's confirmed and what to do

TL;DR. On November 16, 2026, Coles told the ASX it is investigating a cyber security incident. It's working with the Australian Cyber Security Centre and outside experts, its stores and website are running, and it says it has found no evidence that customer, team or supplier data was compromised or removed. It hasn't said what kind of attack this was or how it started. For security teams, the Coles cyber attack is less a lesson about Coles than a forecast for this week: Coles-themed phishing, reused passwords tried against other logins, and suppliers asked to "update details".

A disclosure is not a diagnosis. Here's what Coles has actually said, what it hasn't, and what's worth doing now.

What happened in the Coles cyber attack?

Coles disclosed the incident to the ASX on Monday morning, November 16. Its updates page, current as at 8:30am that day, says Coles is working with the Australian Cyber Security Centre and global cyber security experts to contain and secure its IT environment.

One service has visibly changed. Coles says a small number of customers reported issues with Liquorland Click and Collect, and Liquorland told customers it has temporarily suspended the service while it investigates, National Liquor News reported. Liquorland stores and home delivery continue.

Coles says it has no indication Flybuys accounts are affected, has found no issues with Coles Plus, Coles Plus Delivery or QuiteLike, and that gift cards work as normal.

What Coles has confirmed and what it hasn't

Confirmed by ColesNot disclosed yet
An incident is under investigation, with the ACSC and outside expertsThe type of incident: ransomware, data theft, or unauthorized access
No evidence of compromised customer, team or supplier data so farThe entry point and when the attacker got in
Stores, app and website operating normallyWhich internal systems are affected
Liquorland Click and Collect issues for a small number of customersWhether any group has claimed responsibility

"No evidence so far" is a statement about what an investigation has found on day one. It isn't the same as "nothing was taken", and Coles doesn't claim it is. It says it will post updates as appropriate.

Separately, ABC News reported that Woolworths is looking into digital gift cards drained over the same weekend. Nothing public connects the two, and it would be a mistake to read one as evidence about the other.

Why the risk this week sits outside Coles

When a household-name retailer discloses an incident, attackers don't need its data to profit. They need its name in the news. Three things follow almost every disclosure like this one, whatever the root cause turns out to be.

  1. Lookalike notifications. Customers have just received a genuine "we're investigating a cyber incident" email. A fake follow-up asking them to "verify your account" or "claim a voucher" has an easy path. Coles says it will never ask for a password or sensitive account details in an unsolicited email or SMS.
  2. Password reuse, tested elsewhere. Coles is telling customers to use a strong, unique password for each account. Attackers read the same advice as a list of where reused credentials might work. Your login endpoints are on that list.
  3. Supplier fraud. Coles has told its suppliers to stay alert, and for good reason. A message that looks like it comes from Coles, asking a supplier to change remittance details or log in to a "new portal", is the cheapest attack in the set.

None of these depend on what happened inside Coles. All of them land on other companies' staff, customers and apps.

What security teams should do this week

A vendor-neutral checklist you can run whether or not you use Nullify:

  1. Warn your own people. Send staff a two-line note: expect Coles-themed emails and texts, and don't act on links in them. Retail-brand lures reach work inboxes too.
  2. Watch your login traffic. Look for a rise in failed logins, many accounts tried from few IPs, or many IPs trying few accounts. Check that rate limits and lockouts apply to your API login and token endpoints, not just the web form.
  3. Check what your auth errors give away. If your API answers "user not found" differently from "wrong password", an attacker can test which leaked email addresses hold accounts with you before trying passwords.
  4. Lock down payment-detail changes. If you supply Coles or any large retailer, confirm every request to change bank details or credentials through a contact you already hold, not one in the message.
  5. Rehearse your own first statement. Coles could say "no evidence data was removed" within hours. Ask whether your logging and egress records would let you say the same, or say anything at all, on day one.

How Nullify helps with the part that's in your code

We don't know how the Coles incident started, and we won't guess. Nullify doesn't investigate breaches, doesn't filter phishing and has no view into Coles' systems.

What we can speak to is the part of this week's risk that lives in your own application. Credential stuffing and account takeover succeed when authentication logic lets them: missing rate limits on an API route, responses that confirm which accounts exist, or session handling that skips a check. Nullify's code analysis looks for authentication and authorization failures, including privilege escalation and business-logic flaws, on every pull request. The AI pentest agent tests authenticated REST and GraphQL API flows and proves which findings an attacker can actually exploit before anyone is asked to fix them.

Fixes arrive as pull requests. Your developers approve every merge.

Frequently asked questions

Was Coles hacked?

Coles disclosed a cyber security incident on November 16, 2026, and is investigating it with the Australian Cyber Security Centre and outside experts. It hasn't said how the incident started or what kind of attack it was, so it's too early to say exactly what happened.

Was customer data stolen in the Coles cyber attack?

Coles says its investigation to date has found no evidence that customer, team or supplier data was compromised or removed. That reflects what the investigation has found so far, and Coles says it will post updates on its Coles Group updates page.

Is the Coles cyber incident email real?

Coles has emailed customers about the incident. Treat any follow-up message with caution: Coles says it will never ask for your password or sensitive account details by unsolicited email or SMS. Check updates by typing colesgroup.com.au/updates into your browser instead of clicking a link.

Is the Coles incident linked to the Woolworths gift card reports?

Nothing public connects them. ABC News reported that Woolworths is investigating digital gift cards drained over the same weekend, but neither company has linked the two, and Coles says its own gift cards work as normal.