# The Voice on the Phone Was Not Your Client **THE TECHNOLOGY BLIND SPOT** Last week, I answered a call from the Federal Reserve Bank. The caller knew my Social Security number. She recited two former addresses I had not used in a decade. She identified a credit card account, described a specific outstanding balance, and informed me that a legal debit would hit my bank account within two hours unless I cooperated immediately. I spent 45 minutes on the line. Not because I believed her. Because I wanted to see how much she had. She had enough. Between the 2015 Office of Personnel Management breach that compromised 21.5 million records, the 2017 Equifax breach that exposed 147 million consumers, and the cascade of smaller exfiltrations that have turned personal data into a commodity, my biographical footprint is available to anyone willing to pay for it. So is yours. So is your client’s. After 45 minutes, I told the caller to proceed. Nothing happened. The Federal Reserve does not maintain accounts for individuals, does not call consumers about debts, and does not threaten legal action. The whole performance was a social engineering operation, built on real data stolen from real breaches, aimed at provoking a real mistake. Twenty-five years of building enterprise security infrastructure taught me to recognize the play. The question that kept me awake that night was not about my phone. It was about yours. ### The Call Your Paralegal Answers Reverse the scenario. A caller phones your firm at 2:15 on a Tuesday afternoon. The caller identifies herself by a client’s name. She provides the client’s date of birth, a partial Social Security number, and the case number from an active litigation matter. She says she is traveling and needs a quick update on the status of settlement negotiations before a meeting. Your paralegal, recognizing the name and the case number, provides the update. Opposing counsel’s latest offer. Your recommended counteroffer. The deposition schedule for the following month. The call lasts four minutes. The caller was not your client. Every fact your paralegal disclosed in those four minutes, case strategy, settlement posture, deposition timing, was information relating to the representation of a client. Under Model Rule 1.6(a), an attorney shall not reveal such information unless the client gives informed consent or the disclosure is impliedly authorized. Your paralegal’s disclosure was neither. It was a disclosure to a non-privileged third party. Under the same doctrine Judge Rakoff applied in United States v. Heppner, the privilege analysis is settled: when a non-privileged third party obtains access to privileged communications, confidentiality is broken. The mechanism of access, a phone call rather than a chatbot, changes the facts. It does not change the test. ### Reasonable Efforts, or None at All Model Rule 1.6(c) requires that a lawyer “shall make reasonable efforts to prevent the inadvertent or unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client.” ABA Formal Opinion 477R, issued in 2017, identifies the factors governing reasonableness: the sensitivity of the information, the likelihood of disclosure if additional safeguards are not employed, the cost of employing those safeguards, and the difficulty of implementing them. The safe harbor is explicit. An inadvertent disclosure does not constitute a violation if the lawyer has made reasonable efforts to prevent it. That safe harbor collapses when the firm has no caller authentication protocol at all. A paralegal who identifies a caller by voice recognition, confirms identity through a date of birth available in any commercial data broker’s database, and then discloses active case strategy has not applied reasonable efforts. The paralegal applied the same verification methods my Federal Reserve caller defeated in the first 30 seconds of the conversation. Rule 5.3 compounds the exposure. Supervising attorneys bear responsibility for ensuring that non-lawyer staff conduct is compatible with the professional obligations of the lawyer. A managing partner who has never asked whether the firm has a protocol for verifying caller identity before staff discuss case details has not supervised. The partner has assumed. Under Rule 1.6(c)’s reasonableness standard, assumption is not a defense. [See “The Conversation That Saves Privilege,” The Technology Blind Spot, March 2026, for the client-facing mirror of this firm-side obligation.] ### The Breach Data Problem Every informal verification method law firms use to confirm a caller’s identity relies on information that has already been stolen. Date of birth. Social Security number. Home address. Mother’s maiden name. The last four digits of a credit card. These are not secrets. They are commodities. The OPM breach alone exposed Social Security numbers, birthdates, addresses, and 1.1 million sets of fingerprints for 21.5 million current and former federal employees. Senator Mark Warner warned in May 2025 that those individuals would remain at risk “likely for the remainder of their lives” because the stolen data is permanent and the government’s identity theft protections were being curtailed. Equifax added 147 million Social Security numbers and birthdates to the open market in 2017. Experian’s 2015 breach exposed 15 million T-Mobile applicants’ records, including SSNs, birthdates, and driver’s license numbers. None of these breaches has an expiration date. The data stolen a decade ago answers the same security questions your receptionist asks today. A caller who can recite your client’s date of birth, case number from a public docket, and the name of the attorney handling the matter does not need to be your client. That caller needs five minutes on a data broker’s platform and a PACER account. Public court filings provide case numbers, party names, attorney names, and hearing dates. Commercial data brokers sell the biographical details that fill the gaps. The combination is lethal: enough public information to open the conversation, enough stolen information to pass the verification, enough confidence to keep the paralegal talking. The Federal Trade Commission testified before the Joint Economic Committee in March 2026 that consumers lost $15.9 billion to fraud in 2025, up from $12.5 billion the prior year. Imposter scams accounted for over $3.5 billion of that total, with more than one million reports filed. The Social Security Administration reported in its March 2026 Slam the Scam campaign that government impersonation complaints alone exceeded 330,000, a 25 percent increase over 2024. These are not exotic attacks. They are high-volume operations built on breach data, executed by professionals who study their targets. ### The Callback That Does Not Protect You For decades, the standard safeguard against phone fraud was the callback. Hang up. Look up the number. Call the person back. If the real person answers, the communication is authenticated. Voice cloning has eroded that safeguard. The technology requires only three seconds of source audio and runs on consumer-grade hardware. Source material is obtainable from a voicemail greeting, a conference presentation, a podcast appearance, or a social media video. In January 2024, a political consultant commissioned an AI-generated robocall impersonating President Biden for $500, and open-source tools have since driven the per-clone cost toward zero. Dark web marketplaces advertise real-time voice cloning services for as little as $30. In February 2024, an Arup employee in Hong Kong transferred $25 million after participating in a video call populated entirely by AI-generated likenesses of real executives. Real-time voice cloning can now sustain a live conversation. A callback to a spoofed number answered by a cloned voice is not a verification. It is a confirmation of the fraud. For law firms, the attack surface is specific. Attorneys’ voices are available from oral arguments, CLE presentations, firm marketing videos, and media interviews. Client voices are available from the same channels, and from the voicemail systems that most firms maintain. A paralegal who calls the client back and “recognizes the voice” has not verified identity. The paralegal has confirmed that the voice sounds familiar. A 2025 iProov study found that only 0.1 percent of participants correctly identified all fake and real media they were shown. In 2026, trusting your ear is not a security control. [See “How Artificial Intelligence Is Fueling More Money Laundering,” The Technology Blind Spot, February 2026, for the financial fraud implications of voice cloning technology.] The exposure varies by practice area, but the vulnerability is universal. In criminal defense, a caller impersonating a client could extract defense strategy, witness lists, or plea negotiation posture, information that in the wrong hands can endanger witnesses or compromise a defense. In family law, a caller impersonating one spouse could extract financial disclosures, custody strategy, or settlement terms that hand the opposing party a tactical advantage they could never obtain through discovery. In corporate and M&A practice, a caller posing as a client’s general counsel could extract deal terms, closing timelines, or regulatory filing strategies. In December 2016, the DOJ charged three individuals with hacking two prominent New York law firms, identified by the Wall Street Journal as Cravath Swaine & Moore and Weil Gotshal & Manges, to steal M&A intelligence for insider trading. Those attackers penetrated networks. A social engineering caller skips the network entirely and walks through the front desk. ### The Friction Objection Friction is the strongest argument against caller authentication protocols. Most callers are legitimate clients. Requiring a passphrase or a callback protocol for every phone interaction creates a barrier that could damage client relationships, slow response times, and make the firm appear bureaucratic. A client who retained you because you answer the phone on the second ring will not appreciate being treated like a suspicious stranger. That objection deserves honest weight. A solo practitioner who represents twelve clients and recognizes each one by voice faces a different risk calculus than a 40-attorney firm where dozens of staff members field hundreds of calls weekly. Proportionality matters. Not every call warrants the same level of verification. But the objection collapses under the weight of Rule 1.6(c)’s own language. The reasonableness factors in ABA Formal Opinion 477R include the sensitivity of the information and the cost of implementing safeguards. A client-specific verbal passphrase, established at the beginning of the engagement and required before any staff member discusses case substance, costs nothing to implement. It takes 30 seconds to establish during the intake call. It adds five seconds to every subsequent conversation. Against that cost, place the consequence: a single successful social engineering call that extracts settlement strategy in an active litigation can shift the outcome of the case, trigger a malpractice claim, and produce a disciplinary referral. The cost-benefit analysis is not close. A legal malpractice insurer’s 2026 advisory to covered firms illustrates the pattern through a composite scenario drawn from reported claims. A caller impersonated a client of an intellectual property firm, provided the client company’s name and enough biographical detail to pass the receptionist’s informal check, and asked a junior associate to reset a portal password. The associate complied. The attacker used the password to access the client’s document repository and download sensitive trade secret filings. When the actual client discovered the breach, the firm’s malpractice carrier bore the claim. The carrier’s post-incident analysis identified the gap: no written protocol existed for verifying caller identity before providing account access or case information. The scenario is composite. The pattern is not. ### What Catherine Does Thursday Call your office manager. Ask one question: what is our current protocol for verifying a caller’s identity before any staff member discusses case details over the phone? If the answer is “we recognize their voice” or “we ask for their date of birth,” you have your answer. There is no protocol. The verification methods your firm uses are the same methods my Federal Reserve caller defeated in under a minute, using data purchased from the same breaches that compromised your clients’ information. Implement a client-specific verbal passphrase. Establish it during the intake call. Record it in the client file. Require it before any staff member, attorney or non-attorney, discusses case substance with any inbound caller. For high-sensitivity matters involving active litigation, pending transactions, or trust account disbursements, add a mandatory callback to the number on file, initiated by your staff, not the caller. Train every person who answers the phone. Document the protocol in writing. Under Rule 5.3, the supervising attorney’s obligation extends to ensuring that non-lawyer staff understand and follow confidentiality safeguards. A protocol that exists in the managing partner’s head but not in the receptionist’s training binder is not a protocol. It is a hope. ### The Test You Already Failed My Federal Reserve caller was good. She had real data, a plausible scenario, emotional pressure, a ticking clock, and the credibility of a government institution behind every sentence. She failed because I have spent a career studying exactly this kind of operation. Your receptionist has not. Your paralegal has not. Your first-year associate, picking up a ringing phone at 5:45 PM on a Friday while the partners are at dinner, has not. You built your firm’s cybersecurity around firewalls, encryption, and access controls. You reviewed your vendor agreements. You encrypted your email. You locked the server room. Then someone called the front desk, said your client’s name, and your staff opened the door from the inside. The voice on the phone was not your client. The question is whether anyone at your firm would have known the difference. ### About the Author JD Morris is Co-Founder and COO of LexAxiom, an Agentic AI platform for the business of law. Over a 25-year career, he has built and scaled enterprise technology products across Dell, EMC, VMware, and Cisco, including the first exabyte eDiscovery platform. He holds dual MBAs from Columbia Business School (Finance) and UC Berkeley Haas (Marketing), a Master of Legal Studies in Cybersecurity Law from Texas A&M, and a Master of Engineering from George Washington University. He writes The Technology Blind Spot on the intersection of emerging technology and law. Connect with him on LinkedIn at http://www.linkedin.com/in/jdavidmorris, on X at @JDMorris_LTech, or on Bluesky at @JDMorris-ltech.bsky.social. ### References 1. American Bar Association. Model Rule of Professional Conduct 1.6, Confidentiality of Information. 2. American Bar Association. Model Rule of Professional Conduct 5.3, Responsibilities Regarding Nonlawyer Assistance. 3. ABA Standing Committee on Ethics and Professional Responsibility. Formal Opinion 477R, Securing Communication of Protected Client Information (May 2017). 4. Federal Trade Commission. Testimony of Lois Greisman Before the Joint Economic Committee, “The Rising Scam Economy.” March 25, 2026. https://www.ftc.gov/news-events/news/press-releases/2026/03/ftc-testifies-joint-economic-committee-agencys-efforts-combat-fraud 5. Social Security Administration. “Social Security and OIG Partner for the Seventh Annual National Slam the Scam Day.” March 5, 2026. https://www.ssa.gov/news/en/press/releases/2026-03-05.html 6. Federal Reserve Bank of New York. Scams Involving the Federal Reserve Name. https://www.newyorkfed.org/banking/frscams.html 7. Federal Reserve Bank of Chicago. Telephone Spoofing Scam Alert. https://www.chicagofed.org/publications/news/2018/phone-spoofing-scam 8. U.S. Office of Personnel Management. Cybersecurity Incident (2015). Approximately 21.5 million records compromised. 9. Warner, Mark R. Letter to OPM Regarding Identity Theft Protections for 2015 Breach Victims. May 16, 2025. 10. United States v. Heppner, No. 1:23-cr-00554 (S.D.N.Y. Feb. 10, 2026) (Rakoff, J.). 11. Identity Theft Resource Center. Statement of James Lee on breach data as fuel for impersonation crimes. Federal News Network, October 2025. 12. Protexure Insurance. “How to Protect Your Law Firm from Social Engineering Fraud.” January 2026. 13. Experian North America. T-Mobile Data Breach Notification. October 1, 2015. Approximately 15 million records compromised. Confirmed by 40-state AG settlement, November 2022. 14. U.S. Department of Justice. Press Release, “Manhattan U.S. Attorney Announces Charges Against Three Chinese Traders.” December 27, 2016. Law firms identified as Cravath Swaine & Moore and Weil Gotshal & Manges by Wall Street Journal reporting. 15. CyberSecureFox. “Real-Time Deepfakes Go Cheap: Dark Web Sells Video for $50 and Voice for $30.” October 2025. 16. iProov. Deepfake Detection Study, 2025. (0.1% participant accuracy rate for identifying all synthetic media.) 17. CrowdStrike. 2025 Global Threat Report. (Voice phishing attacks increased 442% from H1 to H2 2024.) 18. Morris, JD. “The Conversation That Saves Privilege.” The Technology Blind Spot. March 2026. 19. Morris, JD. “How Artificial Intelligence Is Fueling More Money Laundering.” The Technology Blind Spot. February 2026. 20. Morris, JD. “Why Hackers Target Law Firms.” The Technology Blind Spot. 2025.

Originally published on LinkedIn Newsletter: The Technology Blind Spot