DisclosureLens
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Premier Needle Arts — August 2021 breach

Clustered 4 filings across 4 jurisdictions · filing window Mar 8, 2022 Mar 9, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

3,026

First → last filing

Mar 8, 2022 Mar 9, 2022

Merge confidence

100%

incident inc_cb5a7dc551484860 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Aug 22, 2021, discovered Aug 22, 2021 — the first regulatory filing landed 198 days later. 3,026 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
198days

Discovered → first regulatory filing

Discovery variance
165days

Range of discovered_at dates across filings

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >30d · 33dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Aug 22, 2021breach begins
Aug 22, 2021discovered · members disagree
notification delay · 198 days
Mar 8, 2022first filing
Mar 9, 2022most recent filing

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

Member cascade — every filing about this breach

  1. MAR 8ME AGME AG noticefirst filing · states nationwide total 3,026day 0
  2. MAR 8MT AGMT AG notice15 MT residentsday 0
  3. MAR 8IN AGIN AG noticestates nationwide total 3,026day 0
  4. MAR 9MA AGMA AG noticemost recent · 41 MA residents+1d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 22, 2021
ME AG
Discovered
Aug 22, 2021MT AGFeb 3, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
ME AG + MT AG + MA AG
Attack vector
Ransomware
ME AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

3,026

Sum of filed state slices

110· 3.6% of stated

96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US3,026
MA41
IN38
ME16
MT15

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing4 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

1 days

Cadence

~1 / 0.3d

vs. multi-state median

8.0× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.