The FBI recently issued a Flash Report outlining how North Korean cyber actors are “aggressively target[ing] companies and individuals in the cryptocurrency and Web3 industries with highly tailored, hard-to-detect social engineering campaigns, stealing billions of dollars in cryptocurrency in recent years.”

The primary tactic used by the North Korean hackers is FaceStealer, which is “a highly effective social engineering scheme that uses imposter versions of popular video conferencing platforms, secretly recorded web cam video, and computer intrusions.”

The scheme goes like this:

1. Threat actors compromise and secretly record victim’s webcam.

2. Threat actors hijack victim’s communication accounts and message victim’s
contacts.

3. Threat actors deliver convincing fake video link to new target.

4. Threat actors lure targets into realistic imposter video chats.

5. Threat actors impersonate original victim with recorded webcam video and trick
target to self-infect.

It is estimated that the FaceStealer campaign has netted North Korean more than $400 million worth of cryptocurrency in the last 18 months. The hackers are able to leverage victims’ webcams to produce deepfakes through invitations to video meetings from stolen accounts of prior victims. The invitations come from legitimate platforms such as Zoom and Teams. When the target joins the meeting, they are met with a prerecorded webcam video of the previous victim that is known by the target in order to build trust. They are also making deepfakes of well-known and influential people in the crypto industry to disarm the target. During the video meeting, the target is told there is a technical error and asks the target to click on a link that then installs malware onto the target’s workstation in order to steal cryptocurrency and use the target’s credentials to access the network.

This sophisticated campaign shows how cyber-attacks are leveraging AI generated content, including deepfakes, to lure victims into providing credentials and content for the threat actors to use against other victims. It is important for companies and individuals to understand how these attacks work so they can educate themselves and their employees on ways to prevent becoming a victim. A more detailed dive into how the FaceStealer attack works can be found here.

On November 11, 2026, a plaintiff sued DraftKings, a sports betting company, alleging that its online sportsbook steers customers into wagers they did not mean to place. Fitzgerald v. DraftKings, Inc., Docket No. 1:26-cv-05993 (D. Colo.). The proposed class action asserts Massachusetts and Colorado consumer-protection claims and unjust enrichment, and the complaint centers on changing odds during bet placement.

The plaintiff alleges that DraftKings sometimes presents bettors with two odds-change prompts, creating a five-step wagering flow, but at other times shows only one. Reportedly, a prominent yellow “Accept Odds and Place Bet” button appears while updated odds and potential payouts receive less visual emphasis. According to the plaintiff, the shifting sequence led her to believe that accepting the first prompt was an intermediate review, not the final step. The alleged problem is not simply that the yellow button drew the eye. It is that the same action appeared at different points in a changing flow, so a bettor who had previously seen another review step could understand “Accept Odds and Place Bet” as confirmation to continue, rather than the act that immediately committed the wager. The complaint therefore puts the consistency of the entire sequence, not just the visibility of odds disclosures, at the center of the dispute.

The plaintiff alleges she inadvertently placed and lost a $10,000 Texans bet and a $25,000 Bills bet in November 2023. She says DraftKings declined to refund the $35,000 wagered. The complaint also points to the Federal Trade Commission’s 2022 staff report, which describes dark patterns as design practices that trick or manipulate users into choices they otherwise would not make.

Dark patterns can arise wherever interface design nudges people toward choices they might not otherwise make. A bright button, a buried fee, or a cancellation path that seems to go on forever can all shape a decision. The line between persuasion and manipulation may depend on what users see, what they miss, and how much effort it takes to choose differently.

A new class action against Polymarket highlights the legal and reputational risks businesses may face when third-party tracking tools operate on their websites. In Grinnell v. QCX LLC, GD-26-011203, in the Court of Common Pleas of Allegheny County, a Pennsylvania plaintiff alleges that Polymarket used Snap Pixel code to collect website communications, including information about a bet he placed on a basketball game, and then transmitted that data to Snapchat without his consent. The complaint alleges violations of the Pennsylvania Wiretap Act.

Privacy risk arises from the way tracking technologies function, not just from what a privacy notice says. Here, the plaintiff alleges that tracking began as soon as a visitor arrived at the site, before users could learn about or consent to the collection and sharing of their communications. He seeks to represent Pennsylvanians who visited Polymarket while the code was present and argues that class treatment is appropriate. The litigation is at an early stage, but it is again a useful reminder for companies to understand what data their websites and apps transmit to analytics, advertising, and social media vendors.

Businesses should inventory the pixels, tags, SDKs, and other tracking tools deployed across their digital properties; identify what each tool collects and where that information goes; and review whether collection begins before users receive notice or can express a preference. Technical testing should confirm how tools behave in practice, including on sensitive pages and during logged-in sessions. Companies should also align consent flows and privacy disclosures with actual data practices, limit data sharing to what is necessary, and assign clear responsibility for approving and monitoring tracking technologies. These steps can help identify and address gaps before they become a source of litigation or customer concern.

On November 16, 2026, the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) issued its long-awaited final rule updating the HIPAA privacy regulations to “support individual access and improve care coordination and case management” (Final Rule). The Final Rule codifies updates first proposed in late 2020 after taking into account comments received in response to that proposed rule and subsequent developments in health care technology and policy.

The Final Rule is expected to be officially published November 19, 2026, and become effective January 18, 2027. Covered entities will then have 180 days to come into compliance with the Final Rule’s requirements (i.e., until July 17, 2027, assuming that publication schedule), which in pertinent part will obligate entities to update Notices of Privacy Practices again after having to do so by February 16, 2026, pursuant to previous HHS HIPAA rulemaking.

The Final Rule includes the following notable provisions, among other key items:

  • Updates to the Individual Right of Access under HIPAA, including to reduce the amount of time covered entities have to respond to access requests to 15 calendar days (down from the current 30), and updating the process associated with requesting access and copies of PHI (including to amend the permissible fee structure to prohibit fees in certain circumstances and to require public posting of estimated fee schedules), and to add new definitions of “electronic health record” and “personal health application”;
  • Revises the scope of permissible “health care operations” to address individual-level care coordination and case management uses and disclosures as part of a covered entity’s permissible health care operations;
  • Expressly permits disclosures of PHI to social services agencies, community-based organizations, home and community-based services providers, and similar entities, to provide “greater clarity” to covered entities regarding the ability to disclose PHI to such entities without an individual’s authorization for individual-level care coordination and case management that may constitute either treatment or health care operations; and
  • Updates processes related to an entity’s notice of privacy practices (NPP), including to eliminate the longstanding requirement to have each individual patient sign a written acknowledgment of receipt of the NPP where the individual has a direct treatment relationship with the entity, and to update NPP content requirements to address individual rights to their PHI and how to exercise the rights.

Notably, as part of its justification for the Final Rule’s updates to current privacy regulations, OCR directly acknowledges how much has changed in health care and health information technology since the privacy rule was enacted in the early 2000s, and since the passage of the omnibus rule updates in 2013.

The Final Rule is significant for the scope of its changes to the HIPAA privacy regulations and for its focus on enhancing care coordination and the many developments in health care that posed challenges under longstanding HIPAA rules. The Final Rule is also significant for its continued focus on the individual right of access, and the more stringent expectations for access rights going forward, which follows a campaign in recent years by OCR of enforcement actions targeting non-compliance with current HIPAA access requirements.

We will continue to analyze specific provisions within the Final Rule and will follow up with additional guidance as needed. Covered entities would be well advised to review the Final Rule and accompanying guidance closely, and to consider what policy and operational changes will be needed to come into compliance with the new requirements.  Covered entities should also keep in mind that new HIPAA security regulatory updates are expected in 2027, and therefore may see many changes on the HIPAA compliance front in the next year.

The post is also being shared on our Health Law Diagnosis blog. If you’re interested in getting updates on developments affecting health care organizations and health policy, we invite you to subscribe to the blog.

On November 16, 2026, California Attorney General Rob Bonta filed suit against OpenAI alleging that its failure “to adequately secure and monitor the testing of its highly capable and increasingly powerful AI models creates a public nuisance by posing a danger to the public and violates California’s Unfair Competition Law.”

The suit cites the Hugging Face hacking, as well as “at least 80 cyber incidents” that were “entirely foreseeable in light of OpenAI’s choice to test models it knew to be dangerous in a flawed and exploitable testing environment without proper oversight.” The suit alleges that OpenAI “refused to provide detailed information about the full universe of incidents known to the company” when asked by the Attorney General’s office, and that it has made false and/or misleading public statements.

The suit states that OpenAI “misled and endangered the public” by developing and testing advanced AI models “without the safeguards and monitoring necessary to adequately protect the public.” The suit requests injunctive relief, civil penalties, disgorgement and abatement.

Agentic AI may change more than the software businesses use. For decades, companies have organized teams around separate applications, CRM, ticketing, quality assurance, and knowledge systems, with people responsible for configuring workflows, managing access, and maintaining integrations. AI agents can coordinate work across those systems and take on some routine tasks, shifting the organizational focus from managing individual applications to achieving business outcomes. That does not make people less important, but it changes their role: employees may spend less time operating workflows and more time setting objectives, exercising judgment, and overseeing how AI performs.

The transition is not automatic: adding AI to existing tools may speed up individual tasks without addressing the handoffs and silos between teams. More capable agentic systems may coordinate processes across functions, but they can also create uncertainty about who is accountable when an agent acts, uses data, or makes a consequential recommendation. Businesses will need to rethink responsibilities, escalation paths, and oversight, not simply deploy new technology and expect existing structures to adapt on their own.

For businesses considering agentic AI, start with a defined, lower-risk workflow and map the people, systems, data, and decisions involved before automating it. Set clear limits on what the agent may do, including when human review or approval is required; assign an accountable owner; and document how the system is tested, monitored, and changed. Review vendor terms, data handling, access controls, recordkeeping, and incident procedures alongside applicable privacy and sector requirements. Finally, involve affected teams early and train them for oversight and exception handling. A pilot should demonstrate not only that the agent can perform the task, but that the organization can govern it responsibly as the work changes.

Smart glasses have grown in popularity. It is estimated that approximately 13.4 million people in the U.S. currently own smart glasses. According to Security.org, most owners are men between the ages of 30 and 44. Although most people don’t own them, 71% of adults are familiar with smart glasses and that they have a camera and can record. Only 20% of adults are confident that they can identify if someone is wearing smart glasses.

A surprising statistic is that when “recording in public” only 4% of users “always” disclose that they are recording people nearby, 7% “often” disclose the recording, 31% “sometimes” disclose the recording but a whopping 46% say they “rarely” or “never” disclose to those around them that they are recording them.

When asked about concern that smart glasses are being used to secretly record videos in public, 72% of individuals are concerned, and the gender gap of concern is wide. This may be a result of men who secretly recorded women, then posted the clips online without their consent. Only 9% of women surveyed said they were not concerned about being secretly recorded.

In addition, there is concern about the ability to pair facial recognition tools “to identify strangers within seconds.” Only 90% of all adults, and 93% of women surveyed were concerned about the possibility of smart glasses having real-time facial recognition.

As a result, 85% of adults “favor a law requiring smart glasses to display a visual indicator when recording. There are real privacy concerns of smart glasses, including their ability to record without consent, and identify bystanders with facial recognition. Because of these concerns, some cities have banned them, and there have been calls for legislation to address these issues.

Nonetheless, since only 20% of individuals think they can even identify if someone is wearing smart glasses, I thought it would be helpful to outline some tips to identify them, and even more importantly, if they are recording in your presence, which come from Techwalla.

  1. The frame of smart glasses are mostly heavier than regular glasses so look at the front of the frame.
  2. The camera of most smart glasses are located in an upper corner of the glasses, which is small and circular. Some cameras are pinholes in the center of the frame, and may be concealed.
  3. Don’t rely on the LED light, as it does not confirm whether audio is recording.
  4. Smart glasses can “passively capture and transcribe ambient conversation throughout the day.” If someone is recording you in a public place, Techwalla has a three-tier response framework which is interesting and can be adopted or tweaked to fit your preference, including “escalation when the situation is serious.”

If you are a user of smart glasses, understand the privacy concerns of those around you and respect those concerns. If you are not a user, be aware of your surroundings, identify if someone is wearing smart glasses and potentially recording you without your consent, and respond appropriately, depending on the circumstances.

In the wake of targeted cybersecurity attacks against European industrial refrigeration manufacturers, the Cybersecurity and Infrastructure Security Agency (CISA), Federal Bureau of Investigation (FBI), Health and Human Services (HHS), U.S. Department of Agriculture (USDA), and the Department of Transportation (DoT) warned industrial refrigeration and cold chain monitoring systems of malicious cyber activity targeting their industry and provided recommendations for preparation and defense.

The alert is targeted toward “[o]rganizations in the Healthcare and Public Health, Chemical, Food and Agriculture, and Transportation Systems Sectors that widely use these systems, including in refrigerated transport services, for automated and remote monitoring of temperatures, continuous temperature logging, defrost cycle management, and energy optimization.”

The warning was in response to a hacking attack into the refrigeration controllers of major supermarket chains of up to 700 French supermarkets that set them to defrost mode overnight, causing the refrigerators to overheat. The cold chain disruption forced the French supermarkets to discard vast stocks of spoiled goods, resulting in losses estimated to total tens of millions of euros. It is believed that the Iranian government was behind the attack. After the attacks in France, similar attacks were launched against Belgium, Luxembourg, and Sweden. The same operators are also believed to be behind attacks against blood banks in France.

The implications of this type of attack are serious and concerning. Common uses for cold chain techniques include food and produce, pharmaceuticals, vaccines, blood and human tissue, and chemicals. These are all products that people rely on every day for existence, and a disruption in the availability of these products could be devastating.

U.S. based companies involved in industrial refrigeration and cold chain services accessible from the internet can be at risk, as hackers can remotely interfere and cause widespread inventory loss and equipment hazards. These companies are urged by CISA “to defend against this activity by using strong authentication, keeping systems updated, identifying any systems that are accessible from the internet, removing unnecessary remote access, and securing any necessary remote access.”

On November 2, 2026, the National Institute of Standards and Technology (NIST) released Small Business Cybersecurity: Non-Employer Firms, a guide for businesses with no paid employees that may also help firms with limited staff or IT resources.

The guide uses six functions from the NIST Cybersecurity Framework: Govern, Identify, Protect, Detect, Respond, and Recover. Before choosing safeguards, a business should know what information it holds, where it is stored, who can access it, and which outside services it relies on. NIST recommends keeping an inventory of important devices, software, data, and suppliers, and tracking the legal, regulatory, and contractual security requirements that apply.

An inventory helps a small business decide which protections deserve attention first. Email, cloud storage, and online banking are good places to start because they can expose sensitive files or money if an account is taken over. NIST recommends enabling multifactor authentication on sensitive accounts, choosing phishing-resistant options where available, and using strong, unique passwords. It also advises using a standard user account for everyday work rather than staying logged in with administrative privileges. Keeping software updated is important for the same reason, as outdated or unsupported programs may leave known security weaknesses unaddressed.

NIST also recommends protecting backups, testing that they can be restored, and keeping at least one copy disconnected from the device. Ransomware can encrypt files on a computer and reach backups that remain connected. An offline copy is less exposed, but it still needs to be tested. A backup that cannot be restored will not help the business recover.

In addition, NIST recommends that small businesses monitor for signs of suspicious activity and prepare an incident response plan before an attack occurs. The guide suggests keeping contact information for legal counsel and incident response professionals in a paper copy and describes steps such as isolating affected devices and checking backups and account settings before restoring systems.

A small business may not always have a dedicated security team, but it still needs clear answers to three questions: what information matters most; how it would recover that information; and who must be contacted if it is exposed. NIST’s guide gives owners a framework for answering them before an incident.

This post was co-authored by William J. Egan, partner in Robinson+Cole’s Litigation group.

In D’Antonio v. Tripadvisor, LLC, Case No. 2684CV00331 (Mass. Super. Ct. Aug. 31, 2026), a Massachusetts Superior Court dismissed a California Invasion of Privacy Act (CIPA) claim over Tripadvisor’s alleged use of a third-party advertising tracker. The plaintiff alleged that the Casale Media tracker collected IP addresses, device metadata, and unique identifiers, matched them to consumer profiles, and shared or sold the resulting information without consent. The court did not decide whether those alleged practices violated CIPA; it held that Tripadvisor’s Terms of Use selected Massachusetts law, which barred the plaintiff from pursuing the claim under California law.

The court relied on the earlier California court’s finding that the plaintiff had entered a valid contract through Tripadvisor’s online registration process. It also concluded independently that Tripadvisor gave reasonable notice of its Terms of Use and that the plaintiff manifested assent by proceeding through two registration screens displaying, “By proceeding, you agree to our Terms of Use.” Because plaintiff’s counsel acknowledged that the claim could not be reframed under Massachusetts law, the court dismissed the complaint with prejudice.

The decision highlights the potential value of well-drafted choice-of-law and forum-selection provisions, while underscoring that their enforceability depends on the circumstances, including the state’s connection to the transaction and the clarity of the online assent process. It does not eliminate CIPA exposure or resolve the merits of website-tracking claims; instead, it illustrates how contractual terms and litigation strategy can shape where and under what law those claims proceed. Companies should review their registration flows to confirm that terms are clearly presented, that users’ affirmative actions are tied to assent, and assess whether their choice-of-law and forum provisions fit their operations and customer relationships.