Cybersecurity

Naples, Florida Accounting Firm Phillips Feldman Group Sends Breach Notices Listing Social Security Numbers: A Client-Data Checklist for CPA, Tax and Financial Firms

Phillips Feldman Group, a Naples, Florida accounting firm, sent notices dated Oct. 30, 2026 about a data security incident; its Massachusetts filing lists Social Security numbers. A client-data, MFA, remote-access and logging checklist for CPA, tax and financial firms before tax season.

Phillips Feldman Group, P.A., an accounting firm in Naples, Florida, has sent notice letters dated October 30, 2026 about "a recent data security incident that may have involved your personal information," and its filing with Massachusetts lists Social Security numbers among the information involved. The firm is offering 24 months of credit and identity monitoring through IDX, with an enrollment deadline of January 30, 2027. For small CPA, tax and bookkeeping firms, the notice is a reminder that a file server full of client returns is exactly what attackers go looking for, and that the notification work can run for more than a year after the break-in.

What has been reported

A sample of the firm's letter was posted among Massachusetts' November 2026 data breach notification letters. ClassActionU, which reviewed that posted copy, says the letter is dated October 30, 2026 and signed from the firm's Naples office, offers IDX monitoring with a $1,000,000 insurance reimbursement policy and managed identity recovery, and otherwise says very little about the incident itself. The Massachusetts filing, as listed by BreachTally, was reported on November 6, 2026, covers 43 Massachusetts residents, and lists Social Security numbers as the information exposed. No total count of affected people has been published.

ClaimDepot, citing state filings, reports a fuller timeline: the firm found suspicious activity on its network on September 16, 2025; an investigation with outside cybersecurity experts found that certain network files could have been acquired without authorization between August 16 and August 17, 2025; and the review of which files and people were involved finished on August 18, 2026. ClaimDepot also reports that a ransomware group calling itself PEAR posted a claim about the firm on September 27, 2025. Notices to affected people began going out on October 30, 2026, according to the same report.

What we are not claiming: The posted letter does not say how the intruder got in, and we are not guessing. The PEAR posting is a criminal group's claim reported by a third party, not something the firm has confirmed. We are not saying any files were encrypted, that a ransom was demanded or paid, that client returns were published, or that anyone's information has been misused. The 43-person figure is the Massachusetts count only, not a total. The detailed dates above come from ClaimDepot's reading of state filings, not from the Massachusetts sample letter.

Why this matters to accounting, tax and financial firms

A small accounting firm's network holds years of client returns, W-2s and 1099s, bank details for direct deposit, and scanned IDs, usually on one file server or a single cloud share. If the reported timeline is right, the files were at risk over two days in August 2025, and the work of figuring out whose information was in them took about eleven months after the firm spotted the problem. That gap is common and expensive. Most of the cost is not the intrusion itself. It is the forensic review, the letters, the monitoring offers, the regulator filings in every affected state and the client calls that follow.

Tax season makes it worse. Filing deadlines don't move for a breach, and a firm that loses access to its files or has to rebuild trust with clients in January is starting the year behind. The FTC Safeguards Rule also expects tax preparers to have a written security program, multi-factor authentication, and a plan for exactly this situation.

What to do this week

  1. Map where client tax data lives. List the file server, tax software databases, document portals, scanned-ID folders, email attachments and any old exports on staff laptops. Delete or archive what you no longer need to keep.
  2. Put MFA on every way in. Remote desktop, VPN, Microsoft 365, the client portal and the tax software's own logins all need multi-factor authentication, including seasonal staff and outside preparers.
  3. Close remote desktop to the internet. If staff connect to the office from home, use a VPN or a managed remote-access tool with MFA, not an open RDP port.
  4. Watch for large file transfers. Make sure your endpoint protection or managed detection alerts a real person on unusual uploads and new remote tools, including on weekends. The reported window here was a weekend in August.
  5. Keep logs long enough to answer "which files." File-access logs that roll over in days force investigators to assume every file was touched, which means more letters and a longer review.
  6. Test your backups before January. Keep at least one copy offline or immutable, and time a real restore of your tax software and file share.
  7. Update your written information security plan. Name who calls your cyber insurer, breach counsel and IT provider, and how you will tell clients if their data is involved.

The takeaway for IT decision-makers

For a small accounting or tax practice, a breach is mostly measured in months of review and letters, not hours of downtime. Keep less client data, require MFA on every login, close open remote access, make sure someone sees files leaving, and keep the logs that prove what was and wasn't touched. Those steps make an attack harder and a notice like this one smaller.

Sources

One accountable technology partner.

Tell us what's slowing your team down. We'll show you exactly how we'd fix it — no pressure, no jargon.

Book a Free Consultation
Book a Free Consultation