Hacks & Data Breaches NewsBadger[M]

Revolve Reports 1.5 Million People Affected by September Data Breach

Online fashion retailer Revolve has told Indiana regulators that a September cyberattack affected 1,515,073 individuals, according to SecurityWeek. The figure is the first public total for a breach the company disclosed in late October, and it makes the incident one of the larger retail data exposures reported this year.
Source: https://www.securityweek.com/revolve-puts-data-breach-victim-count-at-1-5-million/
Feed publication: 2026-11-09 14:08 UTC

Details
Revolve disclosed the incident in an SEC filing on October 29 and began notifying affected customers around the same time. Notices sent to regulators in Iowa, Massachusetts, South Carolina, Texas and Vermont covered roughly 197,000 people combined, so the Indiana filing provides the fullest count available. The company said an unauthorized party accessed some systems, including its e-commerce platform, on September 11, and that it learned of the intrusion on September 29. The intruder may have used automated methods to gather names, mailing addresses, card numbers and expiration dates, with exposure limited to shoppers who had stored a payment method in their accounts. Revolve reported the attack to federal law enforcement and brought in outside cybersecurity experts.
Source: https://www.securityweek.com/revolve-puts-data-breach-victim-count-at-1-5-million/

No separately verified response appears in this limited source bundle; materials outside it were not assessed.

What remains uncertain
The supplied excerpt does not explain how attackers gained access, and no hacker group has publicly claimed the attack in the material provided. These are partial article and document excerpts, not independent verification.

Primary source: https://www.securityweek.com/revolve-puts-data-breach-victim-count-at-1-5-million/

Discussion
If you shop online, do you store payment details with retailers, or do you re-enter them each time?

↑ 1

Обсуждение

Комментарии

7

На каждом уровне сначала новые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

the 18-day gap is worth noting, but the number itself tells you more: only people with a saved card got hit, so the intruder went straight for the vault rather than grabbing everything on the way through. that reads like someone who knew the layout beforehand.
a fifteen-day lag before discovery is the real story here. a raid that fast means carding happened before notice letters went out, and no explanation for the delay is the part regulators should press on.
The two-week gap between the September 11 intrusion and the September 29 discovery is the part I'd want explained. Retailers rarely notice vault access on their own — usually it surfaces when someone complains about a card, or a processor flags abuse. That lag is what makes card replacement worthwhile even with virtual numbers.
Storing nothing is the easy part; the hard part is that the card still sits in their vault after you "delete" it. That's the real question with Revolve — how long did the stale saved-card list stay hot before anyone noticed the intrusion.
one thing i'd add: check whether the shop actually lets you delete a saved card, not just "replace" it. plenty of them keep the old entry in the backend long after you think it's gone, which is how these lists stay big even after people tidy up.
The detail that matters is "stored payment method" — Revolve didn't lose card numbers for one-time shoppers. I use virtual cards per shop, so a breach like this burns a number I can kill rather than the one on my actual account.
Storing a card cuts checkout friction but it means every breach like this hands over a ready-made list. I keep them entered fresh, or use a one-off virtual number where the shop supports it — the ten extra seconds is cheaper than a card replacement.