科技 · 客户数据泄露
ASOS 黑客窃取了客户搜索记录,也窃取了让诈骗看起来可信的联系方式
攻击者提供的样本中,联系方式和购物搜索记录同时出现。ASOS 称,财务信息和密码未遭访问,但客户仍未获得关于哪些人的记录被窃取的确切说明。
原语言视频
文字实录 · 正在加载
译自英文原文。
新闻追踪第 3 天
1 篇报道32 家媒体42 个来源2 个视频
一条知道你最近在买什么的诈骗信息,比随机发送的信息更难让人置之不理。这正是 ASOS 扩大披露的泄露事件带来的实际风险:黑客获取了客户档案,其中既有联系客户的方式,也有他们在这家零售商网站上的搜索记录。公司称,支付信息和密码未遭访问,但这些信息未被获取,并不意味着其他信息无害。2 3
截至 2026 年 10 月 8 日,ASOS 已告知客户,黑客掌握了可能涉及数百万用户的详细档案。BBC 报道称,攻击者提供的样本包含姓名、地址、电话号码、电子邮件地址、客户编号和网站搜索记录。ASOS 尚未披露受影响人数、被窃取的档案数量或下载的信息总量。“可能涉及数百万”指的是可能的规模,并非经确认的泄露总数。2
据报道,搜索内容包括“reclaimed vintage”“glamorous wide fit”和“Asos petite”。如果将某人的兴趣与其电子邮件地址或电话号码结合起来,欺诈者便可能借此编造出令人信服的购物关联。这是信息暴露带来的风险,并非有证据表明某位客户已遭诈骗,或相关记录已被公开发布。搜索内容示例来自《卫报》转载的 BBC 报道。2 3
该样本既不能证明每份档案包含哪些内容,也不能说明完整数据集的规模。ASOS 自己的声明指出,姓名、联系方式和“某些非个人账户相关信息”遭到访问,但没有完整界定最后一类信息。完整的客户电子邮件和数据集并未提供给外部独立审查。尽管如此,这份更完整的说明实质上取代了公司最初关于基本个人信息可能遭到访问的警告。2 3
从恶意信息到更完整的披露
数十名收件人告诉 BBC,他们收到了该通知,但这并非收件人总数。SBS 报道称,澳大利亚的手机上也收到了该信息,表明其传播范围并非局限于英国。但通知的送达时间也不能证明入侵或下载何时开始。10 月 6 日至 7 日的报道描述称,ASOS 应用和网站运行正常;购物服务是否可用与客户信息是否受到保护,是两个不同的问题。1 4
登录信息遭窃,访问途径仍未查明
ASOS 表示,攻击者冒充可信联系人,骗取一名员工账户的登录凭证,随后利用这些凭证访问第三方平台上的信息。攻击者使用一项未具名服务下载了客户数据。这是通过冒充他人窃取凭证的说法,并非已证实底层数据平台存在技术漏洞。被访问的服务、账户权限和访问时间范围仍未披露。2 3
通知声称:“我们已完全控制 Snowflake 实例。”Snowflake 表示,其调查仍在进行中,截至当时尚未发现其平台遭到入侵。自称 Xuanyewen 的网络犯罪分子另行告诉 BBC,他们通过 Simon AI 获取了信息;该平台被描述为基于 Snowflake 构建。这一具体途径尚未得到独立证实。1 2
与 ASOS 有关的实例、基于 Snowflake 构建的服务,以及 Snowflake 底层平台,并非可以互换的概念。凭证遭窃可能让人进入客户环境,但不能据此证明基础设施提供商本身遭到入侵。现有调查结果尚未确定究竟哪个环境遭到访问。通知中带有勒索性质的威胁,也不能证明勒索金额或付款情况。1 2
据 Infosecurity 报道,Group-IB 的研究将通知中出现的 Telegram 频道 xuanyewengateway 关联账户,与此前的游戏道具交易活动联系起来。OSINTsights 区分了该频道于 10 月 6 日创建的时间和其管理员更早的网络活动记录。这种关联基于账户历史,并不等于确认现实世界中的攻击者身份,也不能证明频道控制者、通知发送者和数据窃取者是同一人。23 39
Cybernews 于 10 月 7 日报道称,研究人员尚未发现能够证明有人持有 ASOS 客户记录的泄露文件或样本。10 月 8 日的披露以及 BBC 对样本的检查,推进了此前的证据情况,但并未证实 Snowflake 遭到全面入侵这一具体说法。26 2
客户目前能确知的情况
ASOS 最新声明称,支付卡信息、银行资料和账户密码未遭访问。这一说法比最初“据信银行卡信息和密码未受影响”的评估更为明确。ASOS 告知客户无需采取行动,同时提醒他们警惕未经请求的联系。网络安全专家 Trevor Dearing 则另行建议,客户可出于预防考虑更改密码,并留意可疑活动;这项建议并不能证明 ASOS 密码遭到窃取。1 2 3
BBC 于 10 月 6 日发布的建议告诉客户,对未经授权的推送通知不予理会,也不要与其互动;该信息包含一个外部链接。此后,Skint Dad 报道了英国国家网络安全中心(NCSC)的建议,即使没有收到通知,也应假设信息可能已泄露。现有 NCSC 一手材料中未显示该建议的确切措辞;预防性指导也不代表认定每位客户的信息都遭到访问。21 14 9
监管方面的沟通已有进展,但正式状态仍不明确。BBC 10 月 6 日的报道称,截至该报道发布时,ASOS 尚未通知英国信息专员办公室(ICO)。10 月 7 日,ICO 公开回应客户的担忧,并建议谨慎对待链接和附件。到 10 月 8 日,ASOS 表示正与执法机构和监管部门合作。现有 ICO 声明和公司的这一说法,均无法确定何时收到正式的数据泄露报告;目前没有依据认定 ASOS 错过了报告期限。1 6 3
这家零售商的业务覆盖面使缺失的受影响人数尤为关键,但不能据此推算出人数。最初的报道提到,其安卓应用下载量超过 1000 万次,年客户数约为 1700 万,业务覆盖 150 多个市场。下载量是累计安装次数,并非受影响人数;年客户数和市场数量反映的是业务规模,也不是泄露事件涉及的人数。1
投资者反应剧烈,但报道中的跌幅数据并不一致。BBC News 于 10 月 6 日报道称,ASOS 股价当天星期二下跌约十分之一。当晚,FRANCE 24 English 报道称,盘中最大跌幅为 12%,收盘下跌 7%。SBS News 于 10 月 7 日报道称,股价隔夜下跌 10%。BBC 和 SBS 的说法未注明具体观察时间或比较价格;盘中波动和收盘变化是不同的衡量指标。1 5 4
英国《金融时报》(FT)的历史股价记录显示,10 月 6 日收盘价为 454.00p,当日最低价为 426.50p。若以 Daily Political 报道的前一交易日收盘价 502.00p 为基准,则两者分别意味着下跌 9.56% 和 15.04%,与 FRANCE 24 的数据不同。由于现有 FT 摘录未显示前一交易日的数据行,这些计算仍有条件限制。Shattered.io 另行报道称,盘中跌幅最高达 13.2%,股价跌至 439p,高于有记录的全天最低价。没有确凿证据表明当天的全部股价波动都由此次泄露事件造成。33 31 5 29
未知
- 最终受影响人数、访问时间范围、完整的服务清单以及经确认的 ICO 通报日期,仍未披露或无法确定。
后续
- 目前尚无完整统计说明哪些人的记录被窃取,也没有查明被盗登录信息如何被用于访问数据。尚未确定下一次公告日期或调查期限。
核心问题已不再是这是否只是通知系统的一次故障。客户档案已经被窃取。尚无答案的是哪些客户的档案遭到窃取;客户仍未获得关于个人信息受影响情况的确切说明。
本报道使用的消息来源
BBC News 提供了最初的通知事件报道 1、扩展后的客户档案报道 2、其 RSS 版本 7、BBC.com 的通知事件报道 24、实时报道 12 25 以及客户建议 21。《卫报》在其商业新闻实时报道中刊载了客户声明 3。SBS News 4 和 FRANCE 24 English 5 提供了广播报道。
官方材料包括 ICO 关于 ASOS 的声明 6、由 Investegate 刊载的 ASOS 公告 8,以及 NCSC 的事件页面 9 和 PDF 文件 10。其他事件报道来自 BleepingComputer 11、Drapers 13、Irish Independent 15、Retail Insight Network 18、SecurityWeek 19 和 Daily Mail 20。
客户指导和其他报道包括 Skint Dad 14、ALLATRA Media 17,以及《独立报》的防护指南 16、扩展版泄露事件报道 22、凭证窃取报道 37 和通知说明 41。Cybernews 提供了较早的证据评估 26。
播出原貌 29 行
- Hackers obtained ASOS customer profiles containing contact details and website searches. The possible scale reaches millions, but no affected-person count is confirmed. Combining shopping interests with ways to contact someone could make fraudulent messages more convincing. How much information was taken, and what can customers actually know about their exposure?
- Searches included “reclaimed vintage,” “glamorous wide fit” and “Asos petite.” Those interests could give an unsolicited message a plausible shopping connection. That is a fraud risk, not evidence that a particular customer has been defrauded or that the records have been publicly released.
- The detailed records include names, addresses, phone numbers, email addresses, customer numbers and website searches. “Potentially millions” describes possible scale, not a verified total. Neither the number of people affected, the number of profiles taken nor the download volume has been disclosed.
- ASOS's disclosure has changed materially. On 6 October, basic personal information, including names and contact details, might have been accessed. By 8 October, detailed profiles were part of the disclosure. The examined sample does not establish what every profile contains or the contents of the complete collection.
- The account-related category still lacks a full definition. Names and contact details were accessed on third-party platforms, alongside information described as non-personal and account-related. That description cannot erase the fuller profile exposure. The complete customer email and dataset were not available for independent examination.
- An attacker impersonated a trusted contact, obtained an employee account's login credentials, then used that access to reach customer information on third-party platforms. An unnamed service enabled the download. This describes stolen-account access, not an established technical vulnerability in the underlying data platform.
- The first access time, download time and duration remain undisclosed. So do the specific services reached and the employee account's permissions. This is an interim explanation, not a completed public forensic reconstruction. Restricting one notification service cannot, by itself, establish the extent of access elsewhere.
- The rogue notification reached phones in the United Kingdom and Australia. It arrived on 6 October at approximately 10:00 British Summer Time, or 09:00 UTC. That timestamps the customer-facing message, not the start of data access, and these locations do not define the breach's full geography.
- The notification threatened a data leak unless recipients engaged with the attackers, and included an external link. Its claim of a fully compromised Snowflake instance remains unverified. There is no established ransom amount or evidence that a customer or ASOS paid the attackers.
- Dozens of recipients reported receiving the message; that is not a total recipient count. ASOS acknowledged it on Tuesday afternoon and restricted access to its notification platforms that day. The exact acknowledgement and restriction times are unknown.
- The app and website were operating normally in the 6–7 October accounts. Continued shopping availability does not undo information already obtained. Customers were advised to disregard the unauthorised notification and not engage with it, rather than follow the link or respond to its threat.
- Snowflake's ongoing investigation had found no compromise of its platform so far. The name Xuanyewen is attached to a separate, unverified claim of access through Simon AI, described as built on Snowflake. The precise environment accessed remains unresolved.
- A customer-associated instance, a service built on Snowflake and Snowflake's underlying platform are different things. Stolen credentials can expose a customer environment without establishing a breach of the infrastructure provider. The employee-credential explanation does not independently validate the attackers' specific platform claim.
- The Telegram channel xuanyewengateway appeared in the notification and was created on 6 October. Its administering account had an earlier online history linked to gaming-item trading. That association suggests an identity reorganized around the incident; it does not identify a real-world attacker.
- The forum name, matching profile or identifier and a verified connection to the intrusion remain unavailable. It is also unproven that the channel controller, notification sender and data thief were the same person. A 7 October finding of no possession-proving samples preceded the 8 October profile disclosure and sample examination; the evidence advanced, without proving full Snowflake compromise.
- Payment-card information, bank details and account passwords were not accessed in the latest company assessment. That is stronger than the initial wording that cards and passwords were not believed impacted. It does not make exposed contact details or search history harmless.
- Customers were told they did not need to take action, while also being warned about unsolicited contact. A separate precautionary recommendation was to change passwords and watch for suspicious activity. That recommendation is not evidence that ASOS passwords were stolen.
- The precautionary warning's verbatim wording and the expert's organisational affiliation are not established. The practical distinction is between a confirmed password exposure—which is not identified here—and taking an extra precaution while the scope of other exposed information remains uncertain.
- The UK data regulator publicly addressed the incident on 7 October and encouraged caution with links and attachments. That establishes awareness, not receipt of a formal company breach notification. On 6 October, ASOS had not informed the regulator as of the account published that day.
- By 8 October, ASOS was working with law enforcement and regulators. Whether and when it formally notified the Information Commissioner's Office remains unclear. No confirmed receipt date or case-specific reporting deadline is established, so there is no supported finding that ASOS missed a deadline.
- Not receiving the push notification does not settle whether information was accessed. Precautionary advice to assume exposure has been described second-hand, but its exact first-party wording is unavailable. It is not a finding that every ASOS customer's information was taken.
- The National Cyber Security Centre's incident page repeated the initial assessment about names, contact details, cards and passwords. Assistance to ASOS was also described, but the available official passage does not establish what was offered or delivered. That gap does not prove assistance or advice was absent.
- The Android app had more than 10 million Google Play downloads; ASOS served around 17 million customers annually across more than 150 markets. Downloads are cumulative installations, not active users or notification recipients. None of these figures supplies an exposed-profile count or a verified breach rate.
- ASOS shares fell on 6 October, but the reported measures differ: around 10% that Tuesday; a 12% intraday maximum and 7% closing loss; and 10% overnight. The around-10% and overnight descriptions do not establish exact observation times or comparison prices.
- The full-day price record gives a 454.00-pence close and a 426.50-pence low. A separately reported previous close is 502.00 pence. The historical-table excerpt did not include the prior-day row, leaving that denominator without a second checked record.
- Using 502.00 pence, the close calculates to a 9.56% decline and the daily low to 15.04%. Another intraday account gave up to 13.2% and 439 pence—higher than the recorded full-day minimum. These remain distinct accounts, not one settled percentage.
- The conditional closing calculation fits “around 10%,” but differs from the reported 7% close. The conditional low-based calculation exceeds the reported 12% maximum. No established evidence assigns the whole day's share movement exclusively to the breach.
- This was more than a notification-system disturbance: customer profiles were obtained. But the total, access window and full service list remain undisclosed. There is no completed public forensic report, law-enforcement outcome, confirmed regulator-notification date or dated next announcement or investigation deadline.
- The answer is that identifying details and website searches are part of the exposure, but its full scale and individual reach remain unknown. Customers still lack a definitive accounting of which records were taken, while names, ways to contact them and shopping searches may now sit together outside the company's control.
来源
42 个来源32 家媒体2 个视频
来源地图
追溯本篇报道的依据。图谱展示其关联;下方链接可打开本文引用的来源。
来源图谱将在您阅读时加载。
译文更新于
修订记录
- r1首次发布。
