HEWLETT PACKARD ENTERPRISE COMPANY — May 2023 breach
Clustered 6 records across 4 jurisdictions: 4 filings and 2 leak-site claims · filed Feb 5, 2025 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_d716c89f70304836 · merged by deterministic · confidence 100%
Litigation Timing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and leak-site claim in this incident
- JUL 16Leak sitemeow postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- JAN 29NE AGNE AG noticefiling day not on record · no count stated—
- FEB 5MD AGMD AG notice33 MD residentsauto-linked+204d
- FEB 5NH AGNH AG notice6 NH residentsauto-linked+204d
- FEB 5MA AGMA AG notice10 MA residentsauto-linked+204d
- FEB 27Leak sitecl0p postmost recent · attacker claim · unverified+227d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 5, 2023 NE AG
- Discovered
- Dec 12, 2023· 221d undetected NE AG + MD AG + NH AG
- Data types
- Identity (basic) · Credentials · PII · Government ID · PCI · Financial account MD AG + NH AG + MA AG
- Attack vector
- Unauthorized Access MD AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Affected residents by state
per-state reported counts
State AGs report only their own residents; teal bars show each state's reported slice.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 23, 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
0 days
Cadence
~1 / 0d
vs. multi-state median
20.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.