Valplast Supply Services, Inc. — October 2014 breach
One linked filing — more sources may join as they report · filed Dec 17, 2014. View entity profile → Other incidents for this victim →
incident inc_dea4f7eeb78b4500 · merged by deterministic
Litigation Timing
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
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- DEC 17NH AGNH AG noticeonly filing · 7 NH residentsday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Oct 29, 2014 – Nov 7, 2014 NH AG
- Discovered
- —
- Data types
- Financial account · PII NH AG
- Attack vector
- Insider NH AG
- Response
- Valplast has taken immediate steps to prevent a recurrence of these breaches of security · Investigating these possible breaches for purposes of determining additional information regarding the extent to which personal information in our database was actually compromised · Pursuing action against the individual responsible 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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.