BreachScout BreachScout Breach Records

Regulator-posted notice

Breach notice filed by 32 Pearls (June 2025)

Organization named: 32 Pearls Provisional: identity as filed, not yet matched to the directory

What the sources say

Washington Attorney General data breach notifications Primary notice

Posted on the Washington Attorney General data breach notifications with a submission date of June 21, 2025.

Organization as reported
32 Pearls
Information types as reported
Name; Social Security Number; Driver's License or Washington ID Card Number; Full Date of Birth; Health Insurance Policy or ID Number; Medical Information
Incident dates as reported
May 19, 2025
Submission date
June 21, 2025
Observed by BreachRecords
2026-10-19 04:56 UTC (revision 25392, page:5:row:49)
Archived copy
Held in the private archive (provenance)

The listing records a filing with the agency; it is not a finding by the agency.

Washington data breach notifications dataset (data.wa.gov sb4j-ca4h) Duplicate filing

Posted on the Washington data breach notifications dataset with a submission date of June 21, 2025.

Organization as reported
32 Pearls, WA
Entity type as reported
Health
Category as reported
Cyberattack; Ransomware
Incident dates as reported
May 19, 2025 to May 22, 2025
Discovery date as reported
May 22, 2025
Submission date
June 21, 2025
Observed by BreachRecords
2026-11-01 20:03 UTC (revision 63692, row:1408)
Extraction
Parsed from a document; extraction confidence 0.85
Archived copy
Held in the private archive (provenance)

The listing records a filing with the agency; it is not a finding by the agency.

Figures, per source

  • 23,550 individuals affected (residents of the reporting state), according to the Washington Attorney General data breach notifications, source date June 21, 2025, revision observed 2026-10-19.
  • 23,550 individuals affected (residents of the reporting state), according to the Washington data breach notifications dataset, source date June 21, 2025, revision observed 2026-11-01.

Each figure is one source's figure with the basis that source gave. Figures from different sources are shown side by side and are not added, averaged or chosen between.

Timeline

Source dates are the dates the sources give. Observation dates are when BreachRecords recorded each revision.

  • Submission date (Washington Attorney General data breach notifications)
  • Submission date (Washington data breach notifications dataset)
  • Observed by BreachRecords (revision 25392)
  • Observed by BreachRecords (revision 63692)
  • Approved by a reviewer

Organizations linked by a reviewer

  • 32 Pearls Named as the filer Provisional: identity as filed, not yet matched to the directory Linked 2026-11-04, method manual.

Archived evidence

  • 264d45f73831ec8fc298837002b836f792a7cfd7f3d6b4d2128484a23223c042
    text/csv, 453,656 bytes, retrieved from Washington data breach notifications dataset, 2026-11-01 20:03 UTC. Archived privately · Provenance · Source page
  • 629911f1f544d6a606bf2ad7ec1507a8fe4e1fea865193f6b47458248488c1f9
    text/html, 155,323 bytes, retrieved from Washington Attorney General data breach notifications, 2026-10-19 04:56 UTC. Archived privately · Provenance · Source page

Records reflect source filings as of the dates shown. BreachRecords is not a regulator.

Request a correction

A record that disagrees with its source, names the wrong organization or duplicates another is corrected after review. This form is about Breach notice filed by 32 Pearls (June 2025). We acknowledge every request within two business days. We reply by email.

The form is being set up. Check back soon.