FEDERALItem 8.01 · voluntaryHackingManufacturingTechnologyManufacturingData ExfiltratedData PublishedLowContained

Heico

bd_91881bd15c577838 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 2, 2023

Filed

Apr 12, 2023

To disclose

6 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

65%

Full breach record for Heico →2 incidents on file

HEICO Corporation identified a cybersecurity incident on March 2, 2023, impacting certain IT systems. The company contained the incident and restored systems. The incident involved the theft of some internal business documents, and on April 7, 2023 the company became aware that information related to the Company was posted on the dark web. The company believes there will be no material financial impact. Investigation is ongoing.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 6 weeks / 41 days

Mar 2, 2023

Discovered

Apr 12, 2023

Filed

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteblack_bastabd_4ad27c64f03e2c882023-04-08 · +3dCandidate

Regulatory filings (1) · sorted by filing gap

Massachusetts State AGbd_b1cc7c6bccfd262f2023-07-27 · +106dVerified by operator

Name: Heico
norm: heico
SEC CIK: 0000046619
Domain: heico.com

Name: Heico
norm: heico
SEC CIK: 0000046619
Domain: heico.com
Industry: ManufacturingllmTechnologyllm

Discovered: Mar 2, 2023
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unknown
Threat actor: External
Regulator citations: Notified law enforcement

During the incident: Took immediate steps to contain, investigate and remediate the incident
Notified law enforcement
Engaged third-party cyber defense firms
Changes made: Affected IT systems have been substantially restored to full operational capabilities
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 6 weeks(41 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

SEC 8-KApr 12 · first · this page

Massachusetts State AG+106d

Pattern: first filing Apr 12, last Jul 27 (MA) — a 106-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 filing

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

SEC 8-K / victim statementThis record

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

Source URL: https://www.sec.gov/Archives/edgar/data/46619/000004661923000071/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Apr 12, 2023
Raw hash: c475218e23963c8be033dde4c2e04ca3676d628843385f2fac942395008e434d

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html26.4 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entityHeico

Victim entityHeico

Incidentdiscovered Mar 2, 2023

Stated responseTook immediate steps to contain, investigate and remediate the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing