Phillips Auto Inc.

One linked filing — more sources may join as they report · filed Apr 28, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

Affected · reported

First → last filing

Apr 28, 2025

incident inc_dde17b971778481d · merged by deterministic

Confirmed breach. discovered Apr 21, 2025 — the first regulatory filing landed 7 days later. 42 individuals reported across the linked filings.

Litigation Timing

Notification delay

7days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

? — ?breach window unknown

Apr 21, 2025discovered

notification delay · 7 days

Apr 28, 2025first & only filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

APR 28ID AGID AG noticeonly filing · 42 affectedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: —
Discovered: Apr 21, 2025
Data types: Identity (basic) · Government ID · PII
Attack vector: Unauthorized Access
Response: Secured all remaining paperwork · Reviewed internal document handling procedures · Initiated an internal investigation

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.