HackingGovernmentGovernmentVulnerability ExploitSupply Chain (3P Vendor)Data ExfiltratedZero-DayCustomer Data InvolvedIdentity (basic)Government IDHighContained

Baltimore County, Maryland

bd_79add972b8719b06 · schema v1 · pii pii-v1

Severity

High

Discovered

Jun 16, 2023

Filed

Aug 16, 2023

To disclose

9 weeks

Affected · nationwide

14,8466 in this filing

Linked

5 filings

Confidence

65%

Baltimore County, Maryland reported a data breach affecting 14,846 individuals due to a third-party vendor incident. The vendor, Pension Benefit Information ("PBI"), was compromised via the MOVEit Transfer software vulnerability. The breach occurred between May 29 and May 30, 2023, and was discovered on June 16, 2023. Affected information includes names and Social Security Numbers. PBI began notifying individuals on August 10, 2023, and offered credit monitoring services.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Jun 16, 2023 → Filed with AG Aug 16, 202361d ⏱ ME AG >30d9 weeks discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 18 days

discovery → filing · 9 weeks / 61 days

May 29, 2023

Begins

Jun 16, 2023

Discovered

Aug 16, 2023

Filed

vs. sector median

2 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_a1d7a1b995de54982023-08-17 · +1dVerified
Montana State AGbd_5d6ade8125836f652023-08-15 · +1dCandidate
New Hampshire State AGbd_5a1bc227829bfc3d2023-08-14 · +2dVerified
Indiana State AGbd_6caa9f673c6401822023-08-10 · +6dVerified

Name: Baltimore County, Maryland
norm: baltimore county, maryland

Name: Baltimore County, Maryland
norm: baltimore county, maryland
Industry: Governmentllm

Discovered: Jun 16, 2023
Breach occurred: May 29, 2023 – May 30, 2023
Undetected for: 18 daysoccurrence → discovery
Materiality determined: —
Notification sent: Aug 10, 2023
Affected individuals: 14,846state + nationwide
Data types: Identity (basic)Government ID
Data elements: Social Security number
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1195 Supply Chain Compromise
Threat actor: External
Initial access: exploit_public_facing

During the incident: Launched an investigation into the nature and scope of the vulnerability's impact.
Conducted a manual review of records to identify affected individuals.
Providing mailed notices to impacted individuals.
Providing affected individuals access to complimentary credit monitoring and identity restoration services through Kroll/Experian.
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 9 weeks(61 days from discovery to filing)
Compliance flags: ME AG >30d · 61d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Jun 16, 2023
→ Filed with AG: Aug 16, 2023
61d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Jun 16, 2023 → Filed with AG: Aug 16, 2023	61d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Indiana State AGAug 10 · first

New Hampshire State AG+4d

Montana State AG+5d

Maine State AG+6d · this page

Massachusetts State AG+7d

Pattern: first filing Aug 10 (IN), last Aug 17 (MA) — a 7-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://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/e95c82b1-804f-46c0-aedf-4eaabbfefb62.shtml
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 16, 2023
Raw hash: 3a1e13c3e0fcfacb498cd894a6969be1d66ed4b85b78ee745eec9a7a0d342323

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityBaltimore County, Maryland

Victim entityBaltimore County, Maryland

Incidentdiscovered Jun 16, 2023

Stated responseLaunched an investigation into the nature and scope of the vulnerability's impact.

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov