Insights · November 19, 2026

What the 2026 law-firm incidents mean for Austin and Texas firms

Law firms remain a target because they hold client confidential information and because their staff, like everyone else, reset passwords, approve multi-factor prompts, and join video calls. The second half of 2026 made that concrete again.

This briefing summarizes public, source-cited incidents and alerts from September and October 2026, then maps them to Texas professional duties and to a short list of technical and operational checks. It is not legal advice, and it does not allege misconduct beyond what the cited sources already say.

If you would rather start with a conservative, public-only review of your firm’s internet-facing exposure, request a free external attack-surface snapshot. For a managed program built for mid-size firms, see cybersecurity for law firms.

What was publicly reported

On 10 September 2026, Reuters reported that Greenberg Traurig said a limited amount of data had been posted on the dark web in connection with a cybersecurity incident, and that Eckert Seamans had also been affected in the same wave of attacks. Read the firms’ own statements alongside the reporting: Reuters, 10 September 2026.

In late October 2026, Canadian reporting and firm statements described cybersecurity incidents at several large Canadian firms. Borden Ladner Gervais (BLG) posted a public statement that it had identified limited unauthorized access to a portion of its Microsoft cloud environment as part of a wider campaign targeting Canadian law firms, and that certain files, including client-related files, were accessed: BLG statement, October 2026. The Globe and Mail reported the same campaign in connection with McCarthy Tétrault, Davies Ward Phillips & Vineberg, Bennett Jones, and BLG, including firm statements that unauthorized parties had accessed certain files or accounts. See Globe and Mail, McCarthy Tétrault and Davies, Globe and Mail, Bennett Jones and BLG, and the later overview “How hackers broke into four of Canada’s top law firms…” (30 October 2026). This post relies on those firm statements and on official reporting; it does not repeat unofficial file-count figures attributed to unnamed sources.

On 28 October 2026, the Canadian Centre for Cyber Security issued alert AL26-028, describing an ongoing help-desk voice-phishing (vishing) campaign targeting Canadian organizations. The alert describes attackers who contact help desks by phone and via Microsoft Teams, impersonate employees, and attempt to obtain password resets or to relay or bypass multi-factor authentication. Official alert: CCCS AL26-028.

That alert is about a technique, not a single victim. The same pattern — a convincing help-desk or collaboration-tool workflow, an MFA prompt, a rushed reset — is not unique to one country. Austin and Texas firms that use Teams, outsourced IT help desks, or shared password-reset procedures should treat the alert as relevant even if they were not named in Canadian reporting.

This sits inside what we describe as Black October 2026: the October wave of major incidents, critical software disclosures, and AI-accelerated attacks. Law-firm vishing is the identity-and-help-desk part of that wave.

What Texas ethics rules already required

Texas lawyers did not need a new statute in October to have security duties.

Rule 1.01 of the Texas Disciplinary Rules of Professional Conduct requires competence. Comment 8 states that a lawyer should keep abreast of changes in the law and its practice, including the benefits and risks associated with relevant technology. Official compilation: Texas Disciplinary Rules of Professional Conduct (PDF). Rule 1.05 addresses confidential information.

Professional Ethics Opinion 680 (September 2018) concludes that a lawyer may use cloud computing or third-party hosting for confidential client information if the lawyer takes reasonable precautions. Those precautions include understanding the technology, reviewing the terms of service, evaluating the vendor’s security, considering encryption, remaining alert to vulnerabilities, and training staff. Texas Center for Legal Ethics, Opinion 680.

Opinion 705 (February 2025) addresses generative AI in Texas law practice. If a firm is putting client information into an AI tool, that tool is in scope for confidentiality and competence, not a side experiment. State Bar of Texas posting of Opinion 705.

None of those authorities requires a particular vendor. They do require more than hoping the IT provider has it covered.

If a firm has a “breach of system security” involving sensitive personal information, Business & Commerce Code § 521.053 generally requires notice to affected individuals without unreasonable delay and not later than the 60th day after the firm determines the breach occurred, and notice to the Texas Attorney General not later than the 30th day if at least 250 Texas residents are involved. Chapter 521; AG overview. Those clocks are statutory. Involve counsel early. See also Texas cybersecurity compliance.

A short list that is still useful after the headlines fade

Firms do not need a 40-page roadmap to make progress this quarter. They need a few controls that match the pattern in AL26-028 and in ordinary phishing:

  1. Help-desk and identity-reset procedures. Callbacks to a known number, a second factor that is not a push the attacker can relay, and a written rule that a Teams message or urgent phone call is not, by itself, enough to reset access.
  2. Email security and phishing resistance, including for billing, wiring instructions, and client-looking requests.
  3. Managed EDR on attorney and staff endpoints, so a compromised mailbox or a malicious attachment has a detection path after the first click. Managed EDR.
  4. Vulnerability management for internet-facing systems, document-management integrations, and any self-hosted tools the firm still runs. October’s PHP and GitLab disclosures are a reminder that “we are a law firm, not a software company” does not mean you are not running software. Managed vulnerability management.
  5. Vendor and cloud due diligence consistent with Opinion 680, including the outsourced IT or help-desk provider itself.
  6. A written incident-response path, including who may speak for the firm and how client-confidential data will be handled during an investigation. Vulnlogic offers an incident-response retainer for $6,000 per year.

If the firm is adopting internal AI research or drafting tools, add a scoped review of those tools. Vulnlogic’s LLM App Assessment is $3,500. See AI / LLM security.

How we can help

Vulnlogic is based in Austin and works with mid-size firms in Texas and nationally. A typical first step is the free external attack-surface snapshot (public information only, not a penetration test). A typical ongoing program is Core at $3,000 per month (up to 100 users), which includes managed EDR, email security, and vulnerability management. Plus is $5,000 and Complete is $7,000, the last of which includes a scoped annual penetration test. See pricing.

We do not guarantee that a firm will not be targeted. We do not give legal advice. We do run a defined security program and help a firm see what is publicly visible before a more formal test.

Contact us · Law-firm services · Black October 2026 overview

Get in Touch

Talk with us about a law-firm program

You can also request a free external attack-surface snapshot in your message, or email contact@vulnlogic.net.

+1-512-402-3026·contact@vulnlogic.net