What is known so far
- Incident
- An unauthorised push notification was sent through an ASOS customer communication channel.
- Possible data
- ASOS says names and contact details may have been accessed.
- Not currently believed affected
- Payment-card information and account passwords.
- Customer position
- The NCSC says all ASOS customers should assume they are affected.
- Service status
- The ASOS website and app remain operational.
What happened?
Some customers received a push notification headed “ASOS HACKED”. It was addressed to the retailer’s data protection and IT teams, claimed that an ASOS Snowflake environment had been compromised and threatened that information would be leaked unless the sender was contacted.
The notification included a link to a Telegram channel. ASOS later apologised to customers, told them to disregard the message and warned them not to click or engage with the external link.
ASOS says it is investigating unauthorised activity involving third-party platforms that it uses to communicate with customers. It says access to the relevant notification platforms was restricted and that it is working with internal and external specialists and the relevant authorities.
What has ASOS confirmed?
ASOS’s current public position
- An unauthorised notification was sent to customers.
- The activity involved third-party platforms used for customer communications.
- Basic personal information, including names and contact details, may have been accessed.
- Payment-card information and account passwords are not currently believed to have been affected.
- The app, website and wider operations are continuing normally.
At the time of writing, ASOS has not publicly confirmed how many customers are affected, every data field involved, whether information was copied or removed, how the access was obtained or how long any unauthorised access may have lasted.
Those are not minor gaps. An initial statement made during a live cyber investigation is rarely the final account of what happened.
The NCSC says all ASOS customers should assume they are affected
The National Cyber Security Centre has issued incident-specific advice. It says that if you are an ASOS customer, you should assume you are affected even if you did not receive the unauthorised notification.
That does not mean every customer’s data has definitely been accessed. It is a precautionary position intended to help customers recognise and resist follow-on scams while the scope of the incident is still being established.
Do not wait for a scam to mention the breach
Suspicious messages may arrive days or weeks after an incident. Treat unexpected ASOS emails, texts, calls and push notifications cautiously, especially if they ask you to follow a link, provide payment details, reveal a security code or act urgently.
Was Snowflake itself hacked?
That has not been established. The notification claimed that an ASOS “Snowflake instance” had been compromised. Snowflake provides cloud technology used by organisations to store, process and analyse data.
Snowflake told Reuters that it launched an investigation and had found no compromise of the Snowflake platform. Its investigation was continuing.
A claim about one customer environment is not proof of a platform-wide breach
Snowflake’s statement does not by itself settle whether an ASOS-specific account, integration or dataset was accessed. Equally, the message sent through the ASOS app does not prove the attackers’ broader technical claim. The route into the systems remains unconfirmed.
The responsible position is to separate three things: the unauthorised notification, which is confirmed; the possible access to names and contact details, which ASOS has acknowledged; and the attackers’ wider claims, which remain unverified.
Why “basic” personal information can still matter
The description “basic personal information” risks making the exposure sound harmless. A name, email address or telephone number may not allow somebody to take money directly, but it can make a fraudulent approach much more believable.
If a criminal knows that somebody is an ASOS customer, they can build a message around a real relationship. The recipient may be less likely to question an email about an ASOS order, payment or refund when a genuine incident has just been widely reported.
Watch for messages claiming that
- an ASOS payment has failed and card details must be entered again;
- a refund is waiting and must be claimed through a link;
- a parcel cannot be delivered until a small fee is paid;
- an unfamiliar order must be cancelled urgently; or
- the customer’s ASOS account must be secured or verified.
The dangerous part is context. A scam that arrives shortly after a real ASOS incident may appear credible before the customer has had time to question it.
What ASOS customers should do now
A proportionate six-step response
Do not open the Telegram link or engage with the sender of the unauthorised notification.
Treat unexpected ASOS emails, texts, calls and push notifications with caution, even where they use your real name.
Open the ASOS app yourself or type asos.com into your browser instead of following a message link.
Review your ASOS account, email account and payment activity for anything you do not recognise.
Change any password that has been reused across different services, and use strong, separate passwords or passkeys with two-step verification where available.
Keep screenshots and records of suspicious messages, attempted account changes or transactions.
Do not panic-reset through a message link
ASOS says account passwords are not believed to have been affected. If you decide to change your password, access ASOS directly through the official app or website. Never use a password-reset link supplied in an unexpected message about this incident.
Do customers need to cancel their cards?
ASOS says it does not believe payment-card information was affected. On the information currently available, customers should not assume that a saved card has been exposed or cancel it solely because of this incident.
It is sensible to check bank and card statements. If an unfamiliar transaction appears, contact the bank or card provider using the number printed on the card, the official banking app or another independently verified route.
A caller knowing your name does not prove they are genuine
Do not reveal full card details, passwords, one-time codes or security answers to somebody who contacts you. End the call and contact the organisation independently.
Does ASOS have to contact affected customers?
UK data protection law does not require every security incident to be announced individually to every customer. The organisation must assess the risk created by the breach, document its decision and apply the statutory reporting and communication thresholds.
The assessment depends on the nature and volume of the data, how easily people can be identified, the safeguards applied and the realistic ways the information might be misused. The word “basic” does not decide that assessment.
A focused question to send ASOS
Please confirm whether my personal information was involved in the incident announced on 6 October 2026, identify the categories of data affected and explain the protective steps you recommend. Please also retain this request and your response as part of the incident record.
Can customers claim compensation?
A possible data breach does not create an automatic payment. A compensation claim would depend on the established facts, whether ASOS failed to comply with its legal duties and whether the individual suffered provable material loss or non-material damage, such as genuine distress.
At this early stage, the cause, scope and consequences remain under investigation. Customers should be cautious about claims firms presenting a speculative payout as guaranteed before those facts are known.
Evidence worth retaining
- The original app notification or a screenshot of it.
- Any incident notice received directly from ASOS.
- Suspicious emails, texts, calls or attempted account changes.
- Bank or card records showing any unauthorised transaction.
- Correspondence asking ASOS whether your data was involved.
- Evidence of any actual financial loss, identity misuse or significant distress.
What remains unanswered?
We still don't know all the details:
- How many customers are affected.
- Exactly which customer data fields were accessed.
- Whether information was viewed only or copied and removed.
- How the unauthorised party obtained access.
- Whether systems beyond customer notifications were involved.
- Whether affected customers will receive individual notices.
- What notifications have been made to data protection regulators in the UK and other countries.
The ConsumerWise view
There is no reason to panic, cancel cards indiscriminately or accept every dramatic claim made by the people behind the notification.
There is equally no reason to dismiss names and contact details as “only basic data”. The most immediate risk is not necessarily somebody entering an ASOS account. It is somebody using the ASOS name, the publicity surrounding the incident and a customer’s real contact details to make the next scam unusually convincing.
For now, customers should avoid the link, use ASOS only through its official app or website, review their accounts and wait for confirmed information about the scale and cause of the incident.
Official sources and reporting
- National Cyber Security Centre: Incident affecting ASOS customersOfficial incident-specific guidance, including the advice that all ASOS customers should assume they are affected.
- Reuters: ASOS shares slide after hackers target online retailerCarries ASOS’s statement, the notification wording and Snowflake’s response.
- The Guardian: ASOS warns customer data may be compromisedReports ASOS’s customer apology, NCSC involvement and the developing investigation.
- UK data regulator: Steps after a personal data breachOfficial guidance on contacting the organisation, monitoring accounts, recognising scams and protecting personal information.
- UK GDPR, Article 33The statutory test for notifying a personal data breach to the UK regulator.
- UK GDPR, Article 34The statutory test for communicating a high-risk breach to affected individuals.
