GLOBALClaimed by MeowFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jul 16, 2024bd_1bed9a57dd205c27
199$
Clustered 3 filings across 3 jurisdictions · filing window Jul 16, 2024 → Feb 5, 2025. View entity profile → Other incidents for this victim →
incident inc_d01960bc8d7f44d1 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Identity (basic) · Credentials
MD NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 12, 2023
When the intrusion reportedly occurred, per the linked filings
Dec 12, 2023
Reported by MARYLAND AG, NEW HAMPSHIRE AG filings
199$
Hewlett Packard Enterprise Company notified the Maryland Attorney General on February 4, 2025, of a data event affecting 33 Maryland residents. On December 12, 2023, a suspected nation-state actor gained unauthorized access to HPE's cloud-based email environment. HPE engaged external experts to contain and remediate the incident. Affected individuals received notice starting January 29, 2025, and were offered 24 months of credit monitoring and identity theft restoration services.
Affected (this filing):
Hewlett Packard Enterprise Company (HPE) notified the New Hampshire Attorney General of a data event affecting 6 NH residents. On December 12, 2023, a suspected nation-state actor gained unauthorized access to HPE's cloud-based email environment. HPE engaged external experts to contain and remediate the incident. Personal information was potentially accessed. HPE began notifying affected individuals on January 29, 2025, offering credit monitoring services.
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.
Affected (this filing): 6