OCEANAIR Inc.
bd_3c76f772594484d1 · schema v1 · pii pii-v1
Full breach record for OCEANAIR Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Boston-based OCEANAIR, Inc. has been a leader in international logistics management services and supply chain solutions since 1983. We help companies manage and grow their supply chain operations by offering a complete range of tailored, innovative, and value-added solutions. OCEANAIR’s services include Freight Forwarding, Customs Brokerage, Import and Export Compliance, and Domestic Trucking. Our extensive global network of partners delivers cost effective multi-lane and multi-modal transportation management. OCEANAIR has offices located in Boston, MA; Portland, ME; Denver, CO; and Providence, RI.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 10, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Montana State AGbd_13ef39e8ca2f142d2024-08-14 · +64dVerified
- Massachusetts State AGbd_15dd9ee741319d352024-08-14 · +64dVerified by operator
- Maine State AGbd_5c5b13966c5ca8f22024-08-14 · +64dVerified
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Jun 10, last Aug 14 (ME) — a 64-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.