filing.firehose

FilingFirehose research · updated 2026-05-09

7.3% of 8-K Item 8.01 filings contain language suggesting a more specific item

We body-text-classified every 8-K filed in the past 21 business days (4,251 filings). Of the 735 that reported Item 8.01 ("Other Events"), 54 (7.3%) had body language matching the patterns we flag for more specific item codes — including 5 suspected cybersecurity incidents (Item 1.05) and 3 suspected officer departures (Item 5.02).

Why this matters

SEC Form 8-K is the "current report" public companies use to disclose material events. Each item code targets a specific event category — Item 1.05 for cybersecurity incidents, 5.02 for officer departures, 1.01 for material agreements, 1.03 for bankruptcy, 3.01 for delisting notices. Item 8.01 is a catch-all for events that don't fit elsewhere.

When a filer routes an event through Item 8.01 that more naturally belongs under a specific code, the disclosure is harder to find. Filings APIs that trust the filer-reported items (as most do) miss it. Investors monitoring for cybersecurity risk who key off Item 1.05 will not see the BiomX cyber-language disclosure that was filed under Item 8.01.

We don't claim every flagged filing is misclassified — language matching is probabilistic. But the rate is high enough to be material: roughly 1 in 14 Item 8.01 filings contains body language we'd flag for a different item. The FilingFirehose 8-K endpoint surfaces the flag via the suspected_buried_events field on every parsed filing.

Breakdown by suspected real item

ItemWhat it coversFilings flagged
Item 1.01Entry into a Material Definitive Agreement27
Item 3.01Notice of Delisting or Failure to Satisfy Continued Listing Rule17
Item 1.05Material Cybersecurity Incidents5
Item 5.02Departure of Directors or Certain Officers3
Item 2.01Completion of Acquisition or Disposition of Assets3
Item 1.03Bankruptcy or Receivership3

Item 7.01 (Regulation FD) — same pattern, smaller

Item 7.01 is the Regulation FD disclosure item — used to share information that might be material non-public. Of 1079 filings using 7.01, 43 (4.0%) contained body language flagging a more specific event. Lower than the 8.01 rate but non-zero.

What we're flagging — concrete examples

From the 21-day window, here are filings where the body-text classifier detected language suggesting a different item than the filer reported. We do not assert misclassification; we surface the flag for the operator to investigate.

Methodology

Every 8-K body is parsed for item-header sections. For each section, we run a keyword classifier with conservative regex patterns derived from SEC item definitions: ransomware/threat actor → 1.05; "resigned"/"chief executive" within a sentence window → 5.02; "material definitive agreement"/"merger agreement" → 1.01; "Chapter 11"/"voluntary petition" → 1.03; "deficiency letter"/"continued listing" → 3.01.

The classifier flags but does not assert. The suspected_buried_events field maps reported item → list of items our patterns matched. False positives exist (especially when 8.01 contents cite or summarize disclosures from other contexts). The aggregate rate is meant to indicate "how often is body-text scanning a value-add?" — for which 7.3% is a meaningful answer.

Try it on every new 8-K

curl -H "X-API-Key: ff_live_..." \
"https://filingfirehose.com/v1/filings/8-k?items=8.01&limit=10"

Each result includes filer_reported_items, detected_items, discrepancy_items (in body but not reported), and the suspected_buried_events map.

This page auto-updates as the analysis re-runs nightly. Methodology and example classifiers are open-source in the filing_firehose repo.