Clustered 2 filings across 2 jurisdictions · filed Mar 30, 2016. View entity profile → Other incidents for this victim →
incident inc_c3fda979f6af4c7c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Government ID · Identity (basic) · Financial
CA NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 22, 2016
When the intrusion reportedly occurred, per the linked filings
Mar 22, 2016
Reported by CALIFORNIA AG filing
Pivotal Software, Inc. filed a New Hampshire Attorney General breach notification on March 30, 2016, regarding a phishing incident occurring on March 22, 2016. An employee was targeted by a fraudulent email impersonating the CEO, which resulted in the unauthorized access of employee personal information.
Pivotal Software, Inc. experienced a phishing incident on March 22, 2016, where an unknown third party sent a fraudulent email impersonating CEO Rob Mee to an employee. The employee responded, providing personal information including 2015 Form W-2s, which contained names, addresses, income information, and Social Security Numbers. Pivotal investigated, notified law enforcement and the IRS, and offered 3 years of identity protection via AllClear ID.
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.