State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings
Northrop Grumman — April 2016 breach
Clustered 4 filings across 4 jurisdictions · filed Apr 19, 2017. View entity profile → Other incidents for this victim →
⚠ 1 cross-filing discrepancy →Merge100%
incident inc_751d996f36aa4816 · merged by deterministic · confidence 100%
Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. Intrusion Apr 18, 2016–Mar 29, 2017, discovered Mar 21, 2017 — the first regulatory filing landed 29 days later. 7 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Each member filing remains the legal record for its jurisdiction.
Litigation Timing
SupplementalNotification delay
29days
Discovered → first regulatory filing
Filing span
0days
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.
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.