Today: The SEC's enforcement director signaled continued scrutiny of exaggerated AI claims and material omissions about AI use and risks. California Privacy Protection Agency staff proposed changes to California Consumer Privacy Act opt-out signal regulations, while Milliman agreed to a proposed $15.5 million settlement over allegedly inaccurate IntelliScript insurance reports.
Enforcement Actions
Russian Authorities Arrest Three VasyGrek Cybercrime Suspects
Summary: Russia's Interior Ministry said authorities dismantled infrastructure associated with VasyGrek, also known as Fluffy Wolf, and arrested three suspected members following an investigation assisted by Kaspersky. Authorities allege the group used phishing, malicious attachments, and remote administration tools to access corporate networks and banking systems; one described incident involved theft of more than 660,000 rubles, approximately $8,000. The suspects face theft and malware-related charges carrying potential prison terms of up to 10 and five years, respectively, if convicted.
- Compliance Action: Review controls protecting accounting staff from fraudulent business-partner emails and malicious financial documents. Require independent verification of payment changes, restrict remote administration software, and preserve relevant email, endpoint, and banking records when investigating suspected fraud. The announced infrastructure disruption should not replace ongoing monitoring.
- Source: The Record
Litigation Updates
Milliman Agrees to Proposed $15.5 Million Settlement Over IntelliScript Reports
Summary: Milliman agreed to pay $15.5 million to resolve a nationwide class action alleging that its IntelliScript reports supplied life insurers with inaccurate health information. The proposed settlement concerns the accuracy of information used in insurance decisions; it should not be treated as a judicial finding that the allegations were proven.
- Compliance Action: Organizations using third-party health or insurance reports should review procedures for validating consequential information, investigating disputed records, and correcting downstream decisions. Identify who owns error escalation across the vendor and insurer, and retain documentation showing how corrections are communicated. Anyone considering a settlement claim should verify eligibility, approval status, and filing dates in the official settlement notice before acting.
- Source: Top Class Actions
Office Depot Faces Washington Commercial Email Class Action
Summary: A new class action alleges that Office Depot sent Washington consumers commercial emails creating a "false sense of urgency," in violation of the state's Commercial Electronic Mail Act, or CEMA. The allegations place promotional message accuracy, rather than simply email volume, at the center of the dispute; they are not established findings of liability.
- Compliance Action: Have counsel review Washington-facing promotional emails for potentially misleading urgency claims. Require marketing teams to substantiate limited-time offers, retain the applicable offer terms and campaign versions, and check that automated follow-up messages remain consistent with the actual promotion. Treat this as a review prompted by litigation risk, not a newly announced legal requirement.
- Source: Top Class Actions
EyeMed Faces Class Action Over Policyholder Data Breach
Summary: A new class action alleges that EyeMed failed to safeguard policyholders' sensitive information, resulting in a data breach. The lawsuit concerns alleged exposure of names, Social Security numbers, and medical and insurance information, creating litigation risk involving both identity information and health-related records.
- Compliance Action: Organizations exchanging information with EyeMed should establish whether their employees' or customers' records were involved and which data categories were affected. Obtain the relevant incident communications, preserve vendor correspondence, and have counsel assess contractual and statutory notification obligations against verified facts. Do not assume that a business relationship alone establishes exposure or that another organization's notification satisfies your own obligations.
- Source: Top Class Actions
Google Takes Legal Action Against X.CPE Botnet Infrastructure
Summary: Google said it took legal action against domains supporting X.CPE, a botnet researchers identified in more than 1.3 million devices across more than 200 countries, predominantly Android TV boxes but also other Android-based equipment. Google and cybersecurity investigators accused manufacturer Videostrong Technology of embedding and monetizing a firmware backdoor; these accusations should remain distinguished from adjudicated findings. Google also cut ties with Videostrong and banned it from manufacturing devices with preloaded Google apps, while coordinating disruption efforts with cybersecurity companies and Japanese police.
- Compliance Action: Review Android-based signage, conferencing, telehealth, and other connected-device inventories for potentially affected equipment and suppliers. An inventory match identifies equipment to investigate, not confirmed infection. Validate affected models and firmware with authoritative technical guidance, isolate devices showing suspicious behavior, and obtain a verified remediation or replacement plan rather than assuming domain disruption or an ordinary uninstall removes a persistent firmware backdoor.
- Source: The Record
Regulatory Guidance
SEC Enforcement Director Signals Scrutiny of AI Disclosure Overstatements and Omissions
Summary: In October 30 interviews with Reuters and Law360, SEC Division of Enforcement Director David Woodcock said the agency is scrutinizing corporate AI disclosures. According to Debevoise's account, that scrutiny includes public companies exaggerating AI capabilities and failing to disclose AI use or risks in a fundamental part of their business. These comments signal enforcement priorities, rather than announcing a new disclosure rule or compliance deadline.
- Compliance Action: Public companies should coordinate legal, technical, finance, and investor-relations review of AI statements in filings, earnings materials, websites, and presentations. Document support for claims about functionality, revenue, productivity, reliability, and staffing effects; distinguish pilots from deployed systems and human-supervised processes from autonomous operations. Assess material AI-related confidentiality, cybersecurity, and operational risks for disclosure, and revisit statements as deployments change. Private companies can apply similar controls to fundraising communications as a risk-management measure.
- Source: Debevoise Data Blog
CPPA Staff Proposes Changes to CCPA Opt-Out Preference Signal Regulations
Summary: California Privacy Protection Agency staff released proposed amendments to California Consumer Privacy Act regulations governing opt-out preference signals. The proposal would expressly identify Global Privacy Control, or GPC, as an example of a signal businesses selling or sharing personal information must process. This is a proposal, not an adopted amendment or a newly effective compliance deadline.
- Compliance Action: Businesses subject to the relevant CCPA obligations should test how their websites and advertising systems recognize and act on GPC signals. Document the signal's path through consent tools, tags, and downstream vendors, and investigate inconsistent behavior. Before scheduling implementation changes based on the proposal, verify the official regulatory text, procedural status, and any applicable adoption or effective dates.
- Source: Covington Inside Privacy
Privacy Developments
EFF Disclosures Detail Postal Service Monitoring of Protest Activity
Summary: EFF says records obtained through Freedom of Information Act litigation show that the Postal Service's internet Covert Operations Program, or iCOP, monitored and circulated information about protests across the political spectrum in 2020 and 2021. EFF states that the government agreed to release three email chains as part of settling its FOIA suit this fall, and that the disclosed records provide limited evidence of internal safeguards. Agency officials also said an external drive containing program emails became inoperable after being dropped, after the underlying messages had been deleted under the retention schedule.
- Compliance Action: Organizations conducting social-media monitoring should document its purpose, authorized users, collection limits, retention periods, and dissemination rules. Public-sector teams should obtain legal review where monitoring implicates protected expression. Records teams should also verify that preservation copies remain accessible and recoverable, particularly when litigation or disclosure obligations apply; this story does not establish a new private-sector surveillance rule.
- Source: EFF
German Officials Receive Apple Spyware Warnings
Summary: Germany's information security agency, BSI, confirmed that lawmakers and public figures were among recipients of Apple spyware threat notifications. According to The Record's account of a local news interview with Digital Minister Karsten Wildberg, BSI advised recipients to assume their devices were infected and immediately replace them. BSI said it did not know how many devices were actually infected rather than targeted, a distinction that matters when assessing exposure and notification obligations.
- Compliance Action: Treat a credible spyware notification as an incident-response trigger, while distinguishing targeting from confirmed compromise in internal records and external communications. Engage qualified mobile-forensics support, assess potentially exposed accounts and sensitive information, and coordinate device replacement with evidence preservation. BSI's replacement advice addressed the notified recipients described in the story, not every organization using Apple devices.
- Source: The Record
Compliance Takeaways
- SEC AI disclosures: Assign joint legal and technical ownership of AI claims. Retain substantiation and review material omissions alongside promotional overstatements.
- CCPA opt-out signals: Test GPC handling where applicable and document downstream behavior. Verify the CPPA proposal's status before treating proposed language as an effective requirement.
- Sensitive-data incidents: For potential EyeMed exposure, establish affected individuals and data categories before determining contractual or statutory notification duties.
- Marketing and decision accuracy: Review Washington-facing email urgency claims under CEMA, and document correction processes for third-party information used in insurance decisions.
- Device and records governance: Investigate potentially affected Android equipment without presuming infection. For spyware alerts, coordinate containment, evidence preservation, and legal assessment; ensure retained incident records remain recoverable.