Revolve has told regulators that 1,515,073 people were affected by the breach of its online shopping platform, after an intruder may have obtained the names, contact details and saved payment card numbers of customers who stored a card in their accounts. The figure is the total Revolve reported to the Indiana Attorney General, reported by SecurityWeek on 9 November. Revolve itself has not published the total in a consumer-facing statement.
The breach happened on 11 September 2026 and was discovered on 29 September, according to SecurityWeek’s report of the Indiana records. Revolve disclosed the incident in a Form 8-K dated 29 October. In the filing, the company said an unauthorised actor “may have obtained, through automated means,” the name, contact information, payment card number and payment card expiration date of certain customers who saved payment information in their online shopping account.
That wording matters. Revolve has not said the card details were definitely taken, and it has not said they were misused. The scale is on the record: the total Revolve reported to Indiana regulators is 1,515,073 people, all of them customers who chose to store a card. If you never saved a card on Revolve, this breach does not touch you.
The first counts were only 13% of the company-reported total
For a week, the only public numbers were the counts in individual state filings. Revolve’s notices to regulators in Iowa, Massachusetts, South Carolina, Texas and Vermont covered roughly 197,000 people combined, SecurityWeek reported on 2 November. The Indiana filing changed that: it lists 10,534 Indiana residents and a total of 1,515,073 people affected. AcidPeak’s breach-notice index, which reproduces the filings, shows the same total on both the Indiana record and the Texas record, which lists 127,200 Texans.
Our calculation, from those two figures: the updated five-state floor of 197,072 was only 13.0% of the company-reported total. The first published floor, 179,259 on 2 November, was 11.8% of it. The gap exists because most state notices carried no resident count or no published total at all. Texas alone accounted for 127,200 people, Massachusetts 46,813, South Carolina 17,813, Iowa 3,918 and Vermont 1,328. Those five numbers add up to exactly 197,072, and the Massachusetts and Iowa figures come from TEISS’s 11 November report. Two more states published counts beyond the five-state figure: Washington reported 24,859 residents and Indiana 10,534, per AcidPeak’s index of the filings. Together the published state counts reach 232,465, about 15.3% of the company-reported total. The five-state floor on its own understated the breach by about 7.7 times.
| State | Residents in filing |
|---|---|
| Texas | 127,200 |
| Massachusetts | 46,813 |
| South Carolina | 17,813 |
| Iowa | 3,918 |
| Vermont | 1,328 |
| Five-state floor | 197,072 |
| Company total (Indiana AG) | 1,515,073 |
State figures from the attorneys general filings, via SecurityWeek, The Record and TEISS. The total is the figure Revolve reported to Indiana’s Attorney General.
There is a second lesson here. The 1,515,073 figure surfaced publicly on 3 November, when Malwarebytes spotted it hidden in data returned by the Texas Attorney General’s site, and flagged it as unconfirmed at the time, because it did not appear on the public listing and Revolve had not confirmed a total. The Indiana filing is what turned it from an unverified search result into a company-reported total. The numbers in this article carry their labels for that reason: the floor was a floor, and the total is the total Revolve reported to regulators.
What happened, in order
11 September 2026: the intrusion. Revolve says an unauthorised party broke into some of its systems, including its e-commerce platform, on that date, according to SecurityWeek’s report of the Indiana filing. The company has not explained how the attackers got in.
29 September 2026: Revolve became aware of the intrusion, per SecurityWeek’s report of the Indiana records. That is 18 days after the intrusion and 30 days before the public disclosure.
29 October 2026: Revolve discloses the incident in a Form 8-K dated that day and sends notification letters to regulators in several states. The filing itself reached EDGAR on 30 October. The filing says the company confirmed the unauthorised activity was remediated, notified federal law enforcement and engaged external cybersecurity experts. It also says the incident caused no disruption to its service and that Revolve does not expect it to have a material impact on its business.
Week before 2 November: customer notification letters begin going out, SecurityWeek reported. Revolve is not providing the affected customers with free identity theft or credit monitoring services, but reminds them to review account statements and remain vigilant for fraud or identity theft.
2 to 9 November: SecurityWeek reports the four-state floor of 179,259 on 2 November, then updates it to 197,072 with South Carolina on 3 November. Malwarebytes flags the 1,515,073 figure as unconfirmed the same day. On 9 November, SecurityWeek reports the Indiana filing, confirming the total. The gap from the 11 September intrusion to the 29 October disclosure is 48 days.
Revolve vs ASOS: the same month, opposite outcomes
Revolve was not the only fashion retailer to disclose a breach in October 2026. ASOS said in its 8 October statement that payment-card information and account passwords were not believed to be impacted, according to Reuters, and when its investigation concluded on 5 November it said they were not accessed. The two cases leave shoppers in different places: Revolve said card numbers and expiry dates may have been obtained, while ASOS said it did not believe payment-card information was affected. No connection between the two incidents has been reported; they are separate incidents at separate companies, both disclosed in October.
| Revolve | ASOS | |
|---|---|---|
| Disclosed | 29 Oct 2026 (Form 8-K) | 8 Oct 2026 (company statement) |
| Payment card numbers | Yes, numbers and expiry dates, per the filing | No, not believed impacted (8 Oct); confirmed not accessed (5 Nov) |
| Passwords | Not stated | No, not believed impacted (8 Oct); confirmed not accessed (5 Nov) |
ASOS figures from the company’s 8 October statement, as reported by Reuters, and the 5 November conclusion of its investigation.
What should I do if I saved a card on Revolve?
Ask your card issuer for a replacement card with a new number, then remove the saved card from Revolve. Card numbers and expiry dates may have been obtained, so monitoring alone leaves the same card usable. Check statements back to September, report anything unfamiliar, and treat any Revolve message asking for card details as phishing.
- Call your card issuer and request a replacement card with a new number and expiry date.
- Check every card statement from September onward and flag any charge you do not recognise to your issuer.
- Remove the saved card from your Revolve account so it cannot be charged through the saved setting again.
- Turn on transaction alerts with your issuer so every future charge reaches you the moment it posts.
- Treat unexpected Revolve emails and texts as phishing and never share card details through them.
- Save the notification letter and note the dates in case you need them for a dispute later.
Revolve’s own consumer notice letter, filed with the Massachusetts Attorney General, advises customers to review payment card statements for unauthorised charges and report them to the card issuer. A replacement card is the step monitoring cannot replace: the number and expiry date may have been obtained, so the old card stays usable until the issuer cancels it.
What to watch next
Four questions remain open. First, whether Revolve explains how the attackers got in; the company has said nothing about the entry point. Second, whether any card details are misused; no confirmed misuse has been reported so far. Third, the security-code question: the privacy-news site Privitly has claimed the stolen data includes security codes, but Revolve’s filing does not mention them, and no other source confirms it, so it stays unconfirmed. Fourth, whether any group claims the attack; none has, and Revolve has not named an attacker.
The company-reported total is now on the record. The total Revolve reported to Indiana is 1,515,073, and the five-state floor of 197,072 is public record. What is still missing is how it happened, and that is the part worth watching.
Update, November 17: two proposed class actions filed
Two proposed class actions have been filed over the breach, and both allege the same September incident. Case summaries list Baltazar v. Revolve Group as filed on 4 November 2026 and McLaughlin v. Revolve Group on 6 November 2026. Both suits allege that an unauthorised third party gained access beginning on or around 11 September, that the breach was discovered on or around 29 September, and that names, addresses and payment card numbers and expiry dates were exposed. The McLaughlin suit puts the affected range at between 180,000 and roughly 1.5 million accounts. The Baltazar suit cites approximately 1,515,073 people, the same total Revolve itself reported to Indiana.
Both cases are allegations only. Nothing has been proven, no court has ruled, no class has been certified, and Revolve had not responded to either suit at the time of writing. The filings answer one of the open questions from this article, whether customers would seek compensation through the courts. They do not answer how the attackers got in, whether any card details have been misused, or whether the stolen data includes security codes.


