HackingTransportationCustomer Data InvolvedFinancial accountFinancial credentialsLow

Maersk Line, Limited

bd_0f51176bd518715e · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 1, 2023

Filed

Jul 20, 2023

To disclose

7 weeks

Affected · nationwide

1093 in this filing

Linked

2 filings

Confidence

50%

Full breach record for Maersk Line, Limited →

Maersk Line, Limited experienced an external system breach on May 24, 2023, which was discovered on June 1, 2023. The breach affected 3 Maine residents, compromising their names in combination with financial account or credit/debit card numbers and their respective security codes or PINs. The company notified the affected individuals electronically on June 5, 2023, and offered one year of identity theft protection services.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Jun 1, 2023 → Filed with AG Jul 20, 202349d ⏱ ME AG >30d7 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 · 8 days

discovery → filing · 7 weeks / 49 days

May 24, 2023

Begins

Jun 1, 2023

Discovered

Jul 20, 2023

Filed

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Maine State AGbd_2e72b6b063a85c702023-07-14 · +6dCandidate

Name: Maersk Line, Limited
norm: maersk line
Domain: maersklinelimited.com

Name: Maersk Line, Limited
norm: maersk line
Domain: maersklinelimited.com

Discovered: Jun 1, 2023
Breach occurred: May 24, 2023
Undetected for: 8 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 5, 2023
Affected individuals: 109state + nationwide
Data types: Financial accountFinancial credentials
Data elements: Financial account number
Attack vector: Unauthorized Access

Changes made: 1 Year of identity theft protection services offered
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 7 weeks(49 days from discovery to filing)
Compliance flags: ME AG >30d · 49d
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 1, 2023
→ Filed with AG: Jul 20, 2023
49d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Jun 1, 2023 → Filed with AG: Jul 20, 2023	49d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

Maine State AGJul 14 · first

Maine State AG+6d · this page

Pattern: first filing Jul 14 (ME), last Jul 20 (ME) — a 6-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/588c537f-5592-4d12-9f7e-a7d698318336.shtml
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 20, 2023
Raw hash: c52802ff109e422edde9e343fe6abd5619a587a6c8765f6a0779d294a6e8e7b5

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityMaersk Line, Limited

Victim entityMaersk Line, Limited

Incidentdiscovered Jun 1, 2023

Stated response1 Year of identity theft protection services offered

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov