United States – The National Association of Insurance Commissioners (NAIC), a key U.S. standard‑setting body for insurance regulation, has confirmed it was the victim of a ransomware attack that exploited a critical vulnerability in its Oracle PeopleSoft systems. The organization said it identified the breach on June 11, 2026, and later detailed the incident in a public announcement on June 23, 2026. According to the NAIC, an unauthorized third party leveraged CVE-2026-35273, an unauthenticated remote code execution flaw in PeopleSoft Enterprise PeopleTools versions 8.61 and 8.62, to obtain credentials and gain temporary access to certain data storage areas before the access was blocked and the affected systems were remediated. United States – The NAIC said it brought in the Federal Bureau of Investigation and external cybersecurity experts to conduct a comprehensive investigation into the incident and to assess the scope of data exposure. Security researchers from Google Threat Intelligence Group and Alphabet’s Mandiant unit confirmed that CVE-2026-35273 had been actively exploited as a zero‑day for at least 14 days, from May 27 to June 9, 2026, before Oracle released a security advisory and mitigation patch on June 10. The cybercriminal group ShinyHunters has claimed responsibility for the attack, stating on a dark web forum hosted on the Tor network that it exfiltrated 3.1 terabytes of data from NAIC systems.
Prepared by Emily Rhodes and reviewed by editorial team.
This attack on the NAIC, a key insurance regulator, could potentially affect your insurance data. It's a reminder to be proactive about your digital safety. Regularly update your software and use strong, unique passwords for your accounts.
Cybersecurity is a shared responsibility. The NAIC is working with the FBI and cybersecurity experts to investigate this breach. While the extent of the data exposure is still unclear, it's a wake-up call for all of us. Worth forwarding if you know someone who needs a nudge to update their passwords.
Not specified in source.
Not specified in source.
No left-leaning sources found for this story.
No right-leaning sources found for this story.
Comments