BYTE FEDERAL, INC.
bd_49c9872bc3fd7264 · schema v1 · pii pii-v1
Full breach record for BYTE FEDERAL, INC. →2 incidents on fileByte Federal Inc. reported a data breach discovered on November 18, 2024, where a bad actor exploited a third-party software vulnerability to gain unauthorized access to a server. The attacker encrypted data and acquired the encryption key. Approximately 58,000 customers nationwide were affected, including 182 in New Hampshire. Byte Federal shut down the platform, isolated the actor, reset credentials, and engaged forensic investigators. The investigation is ongoing.
J jump to incidentP pin to compareR raw source
Incident timeline
Nov 18, 2024
Discovered
Dec 13, 2024
Filed
vs. sector median
6 wks faster
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Oregon State AGbd_daeb670bbf3e3f522024-12-13Verified
- South Carolina State AGbd_f41748cfed1fc8a22024-12-13Verified
- Montana State AGbd_0db76d11ece12d452024-12-11 · +2dCandidate
- Massachusetts State AGbd_111cf969e08f8a6a2024-12-11 · +2dVerified
Show 3 more filings ↓Show fewer ↑up to 3d gap
- California State AGbd_43871576fda331702024-12-11 · +2dVerified
- Maine State AGbd_8379555c684c474b2024-12-11 · +2dVerified
- Vermont State AGbd_bac8660828954ab92024-12-16 · +3dVerified
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Dec 11 (MT), last Dec 16 (VT) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.