MalwareTechnologyInformationRansomwareRansom DemandedCustomer Data InvolvedIdentity (basic)Government IDFinancial accountHealth (basic)MediumContained

Marlabs, Inc.

bd_f9875622f50ce95b · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jan 5, 2022

To disclose

—

Affected

Not disclosed

Linked

6 filings

Confidence

65%

Full breach record for Marlabs, Inc. →

Marlabs, Inc. experienced a ransomware incident on or around June 20, 2021. The unauthorized access potentially exposed personal information including names, addresses, SSNs, financial account details, passport numbers, and health insurance information. The company engaged cybersecurity experts and federal law enforcement, and offered identity theft protection services to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

Jun 20, 2021

Begins

Jan 5, 2022

Filed

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Montana State AGbd_3107df25a626669e2022-01-05Candidate
Maine State AGbd_59e7f71978215ca02022-01-05Verified by operator
Massachusetts State AGbd_9c0a8dcdc100cd8d2022-01-05Verified
Indiana State AGbd_a924f88032fe8e402022-01-05Verified

Show 1 more filing ↓up to 5d gap

New Hampshire State AGbd_42d6976b7f6f59eb2022-01-10 · +5dVerified

Name: Marlabs, Inc.
norm: marlabs

Name: Marlabs, Inc.
norm: marlabs
Industry: Technologyllm

Discovered: —
Breach occurred: Jun 20, 2021
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDFinancial accountHealth (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement

During the incident: Engaged with federal law enforcement to assist in the investigation
Began a deep technical review with the leading cybersecurity experts
Arranged for complimentary identity theft protection services through IDX
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 · 6 filings · 6 states

View merged incident ↗

Montana State AGJan 5 · first

Maine State AGJan 5 · first

Massachusetts State AGJan 5 · first

Indiana State AGJan 5 · first

California State AGJan 5 · first · this page

New Hampshire State AG+5d

Pattern: first filing Jan 5 (MT), last Jan 10 (NH) — a 5-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-549693
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 5, 2022
Raw hash: a062b5fe41ef2a153826395369b1c3e3373a9be826bd2cd8aa2b703dbd1c7cff

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityMarlabs, Inc.

Victim entityMarlabs, Inc.

IncidentRansomware

Stated responseEngaged with federal law enforcement to assist in the investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov