DisclosureLens
UnknownTechnologyManufacturingInformationCustomer Data InvolvedPIIIdentity (basic)LowContained

Heico

bd_ed8938c831fb6d97 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Dec 19, 2023

To disclose

—

Affected

1state residents only

Linked

5 records

Confidence

65%
Full breach record for Heico →

HEICO Corporation notified one New Hampshire resident of a data incident on December 19, 2023. The company rebuilt affected servers, deployed enhanced monitoring, and offered credit monitoring services. The specific nature of the breach and data types were not detailed in the filing, though PII was implied by the credit monitoring offer.

Leak gap clock✗ Leak >180d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Dec 19, 2023

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 5 records about the same incident.View merged incident
A leak claim by black_basta about this victim was first seen 255 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Filing propagation · 4 filings · 3 states

View merged incident ↗
SEC 8-KApr 12 · first
Massachusetts State AG+106d
Maine State AG+251d
New Hampshire State AG+251d · this page

Pattern: first filing Apr 12, last Dec 19 (NH) — a 251-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.