Grayback Forestry Data Breach
The 2026 Grayback Forestry data breach was a data security event dated January 5, 2026 that affected 5,026 people in total. The Indiana Attorney General's current breach report publishes the exact total.
Exposed Data Types
2- Names
- Social security numbers
About This Breach
Grayback Forestry, a wildfire suppression, fuels management, forest restoration, and emergency-support services company, notified affected people on March 13, 2026. The Indiana report lists 13 residents and Massachusetts's official record lists 6 residents in those states; both are subsets within the nationwide total.
What Is Known About the Event?
Public state records date the event to January 5, 2026. The sample notice confirms a data security event that may involve personal information but does not disclose the initial access method, affected systems, duration, whether data was removed, or the responsible person or group.
What Information Was Affected?
The sample letter says names may have been involved together with other recipient-specific information, which is redacted in the sample. Massachusetts's official breach report marks Social security numbers as an affected data type. Public documents do not provide a broader common list, so each recipient should rely on the scope stated in their own notice.
How Did Grayback Forestry Respond?
The company said it took steps to complete an investigation, reviewed its policies and procedures, and implemented additional security measures. It offered affected people 24 months of complimentary credit monitoring and identity-restoration services through CyEx Financial Shield Complete.
What Should Affected People Do?
Notice recipients should regularly review credit reports for unfamiliar accounts, inquiries, or address changes. A free credit freeze or fraud alert may be appropriate when a Social Security number is involved, and unexpected activity in tax or benefit accounts should also be monitored. Links using the Grayback Forestry or Financial Shield name should be verified against the notice letter or a known official company channel.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
