HackingTransportation & LogisticsTransportationStolen CredentialsCapture Stored DataData ExfiltratedTargetedIdentity (basic)Government IDHealth (basic)MediumContained

SEACOR HOLDINGS INC.

bd_a0994b551b5a0ca7 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Oct 11, 2022

Filed

Jan 12, 2023

To disclose

13 weeks

Affected

Not disclosed

Linked

4 filings

Confidence

66%

Full breach record for SEACOR HOLDINGS INC. →

SEACOR Holdings Inc. notified consumers of a security incident where an unauthorized actor accessed server folders between August 31 and September 3, 2022. The incident exposed names, passport numbers, merchant mariner numbers, and health information. SEACOR engaged a cybersecurity firm and implemented enhanced security tools.

J jump to incidentP pin to compareR raw source

Vermont clock✗ VT AG >45 bday13 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 41 days

discovery → filing · 13 weeks / 93 days

Aug 31, 2022

Begins

Oct 11, 2022

Discovered

Jan 12, 2023

Filed

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Maine State AGbd_f511e70d439343382023-01-12Candidate
Massachusetts State AGbd_15c78f7ba05567a52022-12-09 · +34dVerified
New Hampshire State AGbd_d4a72d456fa4262e2022-12-09 · +34dVerified

Name: SEACOR HOLDINGS INC.
norm: seacor holdings

Name: SEACOR HOLDINGS INC.
norm: seacor holdings
Industry: Transportation & Logisticsllm

Discovered: Oct 11, 2022
Breach occurred: Aug 31, 2022 – Sep 3, 2022
Undetected for: 41 daysoccurrence → discovery
Materiality determined: Oct 11, 2022
Notification sent: Jan 12, 2023
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDHealth (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Initial access: valid_credentials

During the incident: Implemented its incident response plan
Took steps to contain the activity
Launched an investigation
Engaged a cybersecurity firm
Changes made: Completed implementation of an enhanced security tool
Will look for additional opportunities to strengthen its existing security measures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 weeks(93 days from discovery to filing)
Compliance flags: VT AG >45 bday
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Massachusetts State AGDec 9 · first

New Hampshire State AGDec 9 · first

Maine State AG+34d

Vermont State AG+34d · this page

Pattern: first filing Dec 9 (MA), last Jan 12 (VT) — a 34-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://ago.vermont.gov/document/2023-01-12-seacor-holdings-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 12, 2023
Raw hash: 99235f8763ec38f61417f2bd702863285e8010934372ded12f8296423f3b9104

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entitySEACOR HOLDINGS INC.

Victim entitySEACOR HOLDINGS INC.

Incidentdiscovered Oct 11, 2022

Stated responseImplemented its incident response plan

ComplianceVT AG >45 bday

Extraction provenanceno artifact recorded

Source provenanceago.vermont.gov