AccidentalFinancial ServicesHealthcareFinanceMisdeliveryCustomer Data InvolvedPHIGovernment IDIdentity (basic)Health (basic)MediumResolved

METROPOLITAN LIFE INSURANCE CO

bd_7df03b0c866e513a · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Mar 28, 2024

To disclose

—

Affected

Not disclosed

Linked

3 filings

Confidence

66%

Full breach record for METROPOLITAN LIFE INSURANCE CO →46 incidents on file

Metropolitan Life Insurance Company notified California residents that electronic dental claim information was misdirected to incorrect dental providers due to a coding transmission error. The incident occurred on November 1, 2023, and was corrected on February 5, 2024. Affected data included names, Social Security numbers or Alternate ID numbers, patient procedure codes, services rendered, benefit amounts, and dependent names. MetLife offered one year of credit monitoring via myTrueIdentity.

J jump to incidentP pin to compareR raw source

Incident timeline

Nov 1, 2023

Begins

Mar 28, 2024

Filed

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

California State AGbd_8e7135923c34a3d32024-04-22 · +25dVerified
Texas State AGbd_5a3f44273ec36ca32024-04-23 · +26dCandidate

Name: METROPOLITAN LIFE INSURANCE CO
norm: metropolitan life insurance
Domain: metlife.com

Name: METROPOLITAN LIFE INSURANCE CO
norm: metropolitan life insurance
Domain: metlife.com
Industry: Financial ServicesllmHealthcarellm

Discovered: —
Breach occurred: Nov 1, 2023
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: PHIGovernment IDIdentity (basic)Health (basic)
Data elements: Social Security number
Attack vector: Unknown

During the incident: Implemented a fix to correct this error on February 5, 2024
Reaching out to the incorrect dental providers and will be asking them to delete the misdirected information
Arranged for each of the patients above to enroll, at no cost to you, in an online three-bureau credit monitoring service (myTrueIdentity) for one year
Changes made: Taking steps to prevent this from happening again
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 2 states

View merged incident ↗

California State AGMar 28 · first · this page

California State AG+25d

Texas State AG+26d

Pattern: first filing Mar 28 (CA), last Apr 23 (TX) — a 26-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-583199
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 28, 2024
Raw hash: d2277a277a06cb5d2dd9eb5e643d5d918d9afccc99b81220c07f51fa08d23979

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityMETROPOLITAN LIFE INSURANCE CO

Victim entityMETROPOLITAN LIFE INSURANCE CO

IncidentUnknown

Stated responseImplemented a fix to correct this error on February 5, 2024

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov