Incident · 8-K Item 1.05
BayFirst National Bank reports customer data exposed at a marketing vendor
Compiled from public records. Updated 2026-11-10. By the cisonews.net Desk.
BayFirst Financial Corp. told the SEC in a Form 8-K Item 1.05 filing dated October 30, 2025 that a third-party marketing services provider had a cybersecurity incident that exposed customer information held for BayFirst National Bank. The information involved name, date of birth, and Social Security or tax identification numbers of some customers, and the filing does not state how many people are affected.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at BayFirst, and when?
The bank learned of the vendor's incident on August 14, 2025. The vendor confirmed on October 28, 2025 that customer data was involved, which is also the earliest event date on the filing.
According to the filing, the vendor began an investigation on learning of the incident and brought in cybersecurity experts. The vendor also told law enforcement. The filing says the event stayed within the vendor's systems.
What BayFirst customer data was exposed?
The filing describes the data as personal information that was accessed without authorization, based on what was known at the time. The word including suggests the list may not be complete, and the filing does not say whether account numbers or other details were involved.
BayFirst reports no sign of misuse so far. It says affected customers will hear from it directly. The filing does not describe the letter, any credit monitoring offer, or a call-center number or enrollment deadline.
Did the incident affect BayFirst's business?
The company gave no estimate of cost or impact. The Item 1.05 disclosure sits in the same filing as the company's third-quarter 2025 results.
Which vendor was involved, and what do state lists show?
BayFirst's filing does not name the marketing vendor. Washington's attorney general lists a report filed on November 26, 2025 by Marquis Software Solutions that names BayFirst National Bank among more than 30 client banks and credit unions. The breach date on that report is August 14, 2025, the same day BayFirst says it was told of the vendor's incident. That report covers 269,773 Washingtonians across all the listed clients, not BayFirst's customers alone. The information it records is name, Social Security number, financial and banking information and full date of birth.
Two other states record the same vendor report, again counting people across all the clients.
| State record | Filed | People counted |
|---|---|---|
| Washington attorney general | November 26, 2025 | 269,773 Washington residents |
| Indiana attorney general | November 26, 2025 | 34,805 Indiana residents (no total given) |
| Massachusetts consumer affairs office | December 3, 2025 | 280,375 Massachusetts residents |
None of these lists says how many of the people counted were BayFirst customers.
What is still unknown?
The filing does not name the marketing provider; the state lists above tie BayFirst to a Marquis Software Solutions report with the same date. It gives no count of affected customers, no date for when customer notices will go out, and no information on when the vendor's incident itself began. It also does not say whether any customers outside the group described as some customers were involved. No amended filing is on record here, so later findings are not covered.
How this disclosure's timing compares
BayFirst Financial disclosed 77 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 financial services incidents on cisonews.net
- ICW Group Holdings, Inc., Breach notice, first disclosed November 13, 2026
- Point72 Asset Management, L.P., Breach notice, first disclosed November 5, 2026
- The Vanguard Group, Inc., Breach notice, first disclosed November 4, 2026
- Hippo Analytics, Breach notice, first disclosed November 3, 2026; 176,128 affected in total (Indiana Attorney General)
- Baanx US Corp, Breach notice, first disclosed October 30, 2026; 6,594 affected in total (Indiana Attorney General)
Sources
- 2026-11-06 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2025 Data Breach Notification Report, published November 6, 2026
- 2026-11-06 · AIndiana Attorney General, 2025 data breach year-to-date report, published November 6, 2026
- 2026-11-06 · AWashington State Office of the Attorney General, data breach notifications list, published November 6, 2026
- 2025-10-30 · ABayFirst Financial Corp., Form 8-K (SEC EDGAR), published October 30, 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.