DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Outed by judge, Wet Seal reveals 2008 breach

Posted on March 30, 2010 by Dissent

After being outed by a Massachusetts judge who felt that the retailer should have disclosed the incident in 2008, Wet Seal subsequently issued a statement acknowledging that they had a security breach that involved the hacking ring led by Albert Gonzalez.

According to Wet Seal’s statement:

In May 2008, we became aware that a criminal group obtained unauthorized access to our information systems in an attempt to steal credit and debit card data of our customers. Through an investigation led by an independent, third-party computer forensics firm, and corroborated by members of the U.S. Secret Service and U.S. Department of Justice who led the government’s prosecution of Mr. Gonzalez, we found no evidence to indicate that any customer credit or debit card data or other personally identifiable information was taken. In working with the major credit card processing agencies, we also have identified no instances of credit card fraud to suggest that any such data was taken.

Not revealed in their statement is whether Wet Seal discovered the breach themselves or were informed by federal investigators. And while the retailer pats itself on the back for responding promptly once they found out, it seems that they simply lucked out, as the indictment of Gonzalez in the New Jersey case indicated that:

In or about January 2008, Company B was the victim of a SQL Injection Attack that resulted in the placement of malware on its network.

In or about January 2008, over an internet messaging service, GONZALEZ sent P.T. a SQL Injection String that was used to penetrate Company B’s computer network (the “Company B SQL String”). The Company B SQL String was programmed to direct data to Hacking Platforms, including the ESTHOST Server and the Ukranian Server.

[…]

On or about April 22, 2008, GONZALEZ modified a file on the Ukranian Server that contained computer log data
stolen from Company B’s computer network.

[…]

Between in or after March 2007 and in or about May 2008, GONZALEZ participated in a discussion over an internet messaging service in which one of the participants stated “core still hasn’t downloaded that [Company B] sh-t.”

From the above, it seems that at any point between January 2008 and May 2008, Gonzalez and his fellow hackers could have downloaded Wet Seal customer data and it is only a matter of Wet Seal’s good fortune that the hackers hadn’t gotten around to it before Wet Seal found out about the breach and secured their server.

Why Wet Seal felt that they were entitled to victim status and that their reputation and privacy should be respected escapes me, as it seems evident that their customers were lucky but still entitled to know that the retailer’s system had been breached. Maybe not entitled by law, but entitled.


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Toys “R” Us Canada customers notified of breach of personal information
  • Kaufman County's data breach was their second one in three weeks
  • Hacking Formula 1: Accessing Max Verstappen's passport and PII through FIA bugs
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
Category: Breach IncidentsHack

Post navigation

← Organizations Rarely Report Breaches to Law Enforcement
Court papers confirm JC Penney as hacking victim →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.