Incident · 8-K Item 1.05
ENGlobal restricts IT access after a threat actor encrypts data files
Compiled from public records. Updated 2026-11-08. By the cisonews.net Desk.
ENGlobal Corporation disclosed in a Form 8-K dated December 2, 2024 that it became aware of a cybersecurity incident on November 25, 2024, in which a threat actor accessed its IT system and encrypted some data files. An amendment filed January 27, 2025 added that the affected portion of the system contained sensitive personal information, and neither filing states how many people were affected.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
The company says it learned of the incident on November 25, 2024. Its preliminary investigation found unauthorized access to the IT system and encryption of some files.
The company reports that it began an internal investigation, engaged external cybersecurity specialists and restricted access to the system. The first filing said access was limited to essential business operations while work continued.
What information was involved
The original filing did not mention personal data. The amendment states that the accessed portion of the system held sensitive personal information. It does not list the specific types of information, and it does not say whose information it was.
The company says it plans to notify affected and potentially affected parties and regulators. The filings do not describe a letter, a call center or an enrollment deadline.
Effect on operations and finances
In December 2024 the company said it had not yet decided whether the incident was reasonably likely to materially affect its finances or results.
The amendment gave the length of the disruption to business applications, including financial and operating reporting systems, as approximately six weeks. It says operations and corporate functions have been fully restored and that the company believes the threat actor no longer has access.
Based on the information it had, the company believes the incident has not had, and is not reasonably likely to have, a material impact, except as disclosed in the amendment.
What ENGlobal filed after the amendment
ENGlobal filed no quarterly or annual report after the incident, so the amendment is the last the SEC record says about it. On March 5, 2025 the company and three subsidiaries filed for Chapter 11 in the Southern District of Texas, Houston Division, and said they would keep operating as debtors-in-possession. On March 28, 2025 it told the SEC it could not file its annual report for 2024, either by the due date or within the extension. The reasons it gave were the Chapter 11 cases and that it could not pay its auditors and other professionals because of liquidity constraints. A Form 25-NSE removing its stock from Nasdaq listing followed on June 4, 2025. None of these filings mentions the cybersecurity incident, and the record does not connect them to it.
| Filed | Filing | What it says |
|---|---|---|
| December 2, 2024 | Form 8-K, Item 1.05 | The original disclosure |
| March 6, 2025 | Form 8-K, Item 1.03 | Chapter 11 petitions filed March 5, 2025 |
| March 28, 2025 | Form 12b-25 (NT 10-K) | Annual report for 2024 will not be filed on time |
| June 4, 2025 | Form 25-NSE | Notice removing the stock from Nasdaq |
Other filers in the log whose record stops after a bankruptcy or a deregistration include Bitcoin Depot and iLearningEngines. Filers that did close out an incident in a later report are in After the 8-K.
What the documents leave open
The filings give no count of affected individuals, no list of data types, no recovery cost and no description of how the actor gained access. The company says it is working with cybersecurity experts to reinforce its system.
How this disclosure's timing compares
ENGlobal disclosed 7 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.
The rule behind an Item 1.05 filing
Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other industrials & manufacturing incidents on cisonews.net
- Plant Construction Company, L.P., Breach notice, first disclosed November 13, 2026
- Southwire Company, LLC, Other public record, first disclosed November 12, 2026
- USA Waste-Management Resources, LLC, Breach notice, first disclosed November 6, 2026
- Cotton Incorporated, Breach notice, first disclosed November 2, 2026
- NCH Corporation, Breach notice, first disclosed October 30, 2026; 5,031 affected in total (Indiana Attorney General)
Sources
- 2024-12-02 · AENGlobal Corporation, Form 8-K (SEC EDGAR), published December 2, 2024
- 2025-01-27 · AENGlobal Corporation, Form 8-K/A (SEC EDGAR), published January 27, 2025
- 2025-03-06 · AENGlobal Corporation, Form 8-K, Item 1.03 (SEC EDGAR), published March 6, 2025
- 2025-03-28 · AENGlobal Corporation, Form 12b-25 (NT 10-K) (SEC EDGAR), published March 28, 2025
- 2025-06-04 · ANasdaq Stock Market, Form 25-NSE for ENGlobal Corporation (SEC EDGAR), published June 4, 2025
- 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.