DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed4 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

AeroGrow International Inc — October 2014 breach

Clustered 4 filings across 2 jurisdictions · filing window Jun 3, 2015 → Jul 9, 2015. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

4 filings

States

2

Affected · reported

not comparable

First → last filing

Jun 3, 2015 → Jul 9, 2015

Merge confidence

100%

incident inc_57252ead5ce44391 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Oct 15, 2014–Jun 10, 2015, discovered May 5, 2015 — the first regulatory filing landed 29 days later. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Notifications rolled out on a 36-day schedule across 4 filings beginning Jun 3, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
29days

Discovered → first regulatory filing

Discovery variance
36days

Range of discovered_at dates across filings

Filing span
36days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✓ CA 60-day OK · 28dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Oct 15, 2014breach begins
May 5, 2015discovered · members disagree
notification delay · 29 days
Jun 3, 2015first filing
Jul 9, 2015most 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. JUN 3NH AGNH AG noticefirst filing · 436 NH residentsday 0
  2. JUN 3CA AGCA AG noticeno count statedday 0
  3. JUL 9CA AGCA AG noticeno count stated+36d
  4. JUL 9NH AGNH AG noticemost recent · 18 NH residents+36d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 15, 2014 – Apr 27, 2015
NH AG
Discovered
May 5, 2015NH AG + CA AGJun 10, 2015CA AG + NH AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI
NH AG + CA AG
Attack vector
Unauthorized Access
NH AG

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 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
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

36 days

Cadence

~1 / 12d

vs. multi-state median

6.0× slower

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.