The SafePay ransomware group has compromised at least 600 organizations across multiple critical infrastructure sectors since August 2024, according to a new joint advisory from CISA, the FBI and international law enforcement agencies. Victims span North America, South America, Europe and Australia.
The advisory identifies SafePay as one of the most active ransomware groups in 2026.
Attackers gain access through stolen credentials, brute-force attacks, compromised VPN accounts and vulnerabilities in internet-facing devices, including firewalls.
Once inside networks, SafePay operators steal sensitive data, disable security protections and encrypt systems. Researchers also observed attackers deleting backup copies and resetting network-attached storage devices to disrupt recovery. The group threatens to publish stolen information if victims refuse to pay.
Jacob Krell, Senior Director: Secure AI Solutions & Cybersecurity, Suzu Labs:
“SafePay hit at least 600 organizations without a single zero-day. The joint advisory from the Cybersecurity and Infrastructure Security Agency (CISA) and the Federal Bureau of Investigation (FBI) lists five vulnerabilities used for initial access, the newest published in September 2024, the oldest patched more than six years ago. Six hundred critical infrastructure organizations had years of free scanner coverage and Known Exploited Vulnerabilities catalog entries for every one of these flaws, and still never got the window to apply them.
“The advisory’s own details show attackers know exactly which systems nobody wants to touch. Two of the five vulnerabilities target Veeam Backup & Replication, and SafePay pairs them with halting the Volume Shadow Copy Service and resetting network-attached storage to factory settings. A firewall reboot might break the plant floor. A backup server restart might void the recovery plan. So the boxes stay running for years on software with public exploit code, because an outage has a name attached to it and an unpatched vulnerability does not.
“That is a scheduling failure, and CISA’s mitigation list treats it as a homework assignment. Until critical infrastructure operators get a funded maintenance window and someone senior who owns the reboot decision, the next SafePay is already inside the perimeter everyone was too afraid to bounce.”
ㅤ
John Strand, Owner, Black Hills Information Security:
“This particular attack is interesting for two pretty mundane reasons. First, they’re going after municipalities and critical infrastructure because, as we keep finding out, these organizations will pay. Look at how many people are affected when services go down. Add the political pressure to get those services restored, and attackers see a good chance of getting paid.
“Second, these are motherhood and apple pie exploitation techniques. We’re talking about advanced AI and exploits being developed incredibly quickly, while a huge number of organizations are still getting hit because of weak passwords and a lack of multifactor authentication.
“That’s what scares me more than the super elite hacks. It’s the standard stuff we still haven’t gotten under control as an industry.”
ㅤ
Josh Marpet, Senior Product Security Consultant, Finite State:
“It should come as no surprise that ransomware is a problem. After all thousands and tens of thousands of organizations have fallen victim to social engineering attacks, technical attacks, and business logic attacks. Wherever these ransomware groups can gain a foothold, they will use it to steal your current data, destroy your backups, and encrypt everything they can get their hot little hands on.
“And at the same time cyber insurance costs, if you include ransomware, are still incredibly high.
“So this group is using exploits that have been around since 2020. Let’s be clear on this, these are some six year old exploits. Oh wait, I’m sorry some of them are from 2024 only two years old.
“What happened to keeping on top of patching? Well, we have so much more software than we ever had before. How do we keep track of it all?
“We engage specialists. Software is built out of Legos. Libraries and functions. If we have a software bill of materials (SBOM), we can easily keep track of what’s there at what version, and if there’s any updates.
“Then updating it just becomes a matter of going down the list. But if you don’t have a software bill of materials, it’s much harder to keep track of a chaotic ever fluid morass.
“It’s 10pm, do you know what software you’re running?”
The fact is that everything needs be on the table. If it’s not, it will get pwned. It is that simple.


Liquibase Warns AI Agents Are Exposing a Critical Gap in Database Accountability
Posted in Commentary with tags Liquibase on October 21, 2026 by itnerdLiquibase is calling attention to a growing accountability challenge as AI agents take on a greater role in changing production systems. Findings from the company’s 2026 State of Database Change Governance Report, published in March, show that 96.5% of respondents report at least one AI or LLM interaction with their production databases, while only 32% always or often create audit-ready database change history. The warning follows new government action on autonomous AI.
On October 12, 2026, the UK government announced it is developing a specialist capability to respond to serious incidents involving AI agents, working with the National Cyber Security Centre, Department for Culture, Media and Sport, and the AI Security Institute. The government said that when such incidents occur, it must be able to quickly establish what went wrong and contain the risks. In the United States, a concept paper from NIST’s National Cybersecurity Center of Excellence focuses on identity, authorization, and auditing for AI agents, noting that agents are often treated as generic service accounts without dedicated accountability controls.
For enterprises, the same implications extend to production databases. Whether investigating an incident or proving control to an auditor, organizations need a reliable record of what changed, who or what initiated it (human or an AI agent), whether it was authorized, and what controls ran. When AI agents generate and deploy database changes, sometimes through shared service accounts, that record is often the hardest evidence to produce.
The Database Audit Readiness Gap
The 2026 State of Database Change Governance Report, based on a survey of 426 database, platform, technology practitioners and senior technology leaders, reveals a gap between how frequently organizations face audits and how consistently they maintain the evidence needed to demonstrate control:
Most organizations have governance processes, but the controls and evidence supporting those processes aren’t always applied consistently. As AI increases the speed and volume of database change, that gap becomes increasingly difficult to manage.
When AI Makes the Change, Who’s Accountable?
The accountability questions haven’t changed: What changed? Who authorized it? Were the right controls enforced? What has changed is how hard they are to answer once AI agents generate SQL and initiate change through automated workflows. In the same survey, 33.6% of respondents report AI-generated SQL interacting with their production databases, and 21.8% report human review if governance controls aren’t embedded upstream.
Organizations can’t rely on someone remembering to review a change, or on reconstructing its history after deployment. Governance has to be enforced inside the delivery process, with the evidence captured as each change happens.
Liquibase Secure 6.0 Brings Continuous Governance to Database Change
As AI accelerates software delivery, organizations need consistent policies, visibility into change activity, and a reliable record of how controls were applied, regardless of whether changes originate with developers or AI agents.
Introduced September 30, Liquibase Secure 6.0 brings these capabilities together in a unified platform to see, govern, and control database change across teams, pipelines, databases, and agents:
The release builds on Agent Safe Governance, which helps enterprises validate, track, and govern database change whether it’s created by people or AI.
It’s Audit Season. Be Audit-Ready. Always.
Audits shouldn’t test your memory. Organizations need to know what changed, demonstrate that the right controls were followed, and produce evidence without reconstructing activity across tickets, logs, and spreadsheets.
To help organizations address these challenges, Liquibase has launched It’s Audit Season, an initiative focused on closing the gap between database change governance and audit readiness.
The campaign draws on findings from the 2026 State of Database Change Governance Report to highlight the risks of inconsistent controls, fragmented evidence, and the growing role of AI in software delivery. It includes a free Audit Readiness Assessment, an audit checklist, and practical guidance informed by the 2026 report.
Audit season comes around. Audit readiness never leaves.
Learn more: www.liquibase.com/auditseason
Leave a comment »