The Clock Is Off Cyberattacks: How AI Changes Your Response

🔍 Read the full analysis: The Clock Is Off Cyberattacks: How AI Changes Your Response on ThorstenMeyerAI.com

Before you orderOffer from Amazon

Get smart everyday buys delivered free with Prime

• Fast, free delivery on millions of items
• Prime Video, Amazon Music and more included
• Member-only deals all year

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

US agencies and Microsoft have reported documented cases of AI-assisted cyber activity, including scripts aimed at industrial controllers and an agentic framework used in attacks targeting cloud tenants. The reports show AI being applied to familiar attack steps, not proof of an autonomous super-hacker, and Microsoft says most of the targeting in its reported campaign was unsuccessful.

A joint advisory published August 18 by the NSA, CISA, FBI, Department of Energy and Environmental Protection Agency says actors used AI-generated scripts against internet-reachable Siemens S7 programmable logic controllers, or PLCs. These industrial computers help operate equipment in sectors including manufacturing, energy, water and chemicals. The agencies describe reconnaissance and capability development and assess that the activity may be preparation for operational effects against critical infrastructure.

In a separate report published October 21, Microsoft Threat Intelligence linked the China-state-aligned actor Storm-0940 to use of ARTEX, an open-source agentic penetration-testing framework, in activity involving the ConnectWise Cloud Backup compromise. Microsoft says the actor used credentials associated with the cloud backup application to attempt sign-ins to more than 2,250 tenants. It recorded over 151,000 failed logons from October 10 to 14, with a peak of 2,900 per minute; Microsoft says none of those attempts succeeded. In several attacks, it said, the path from initial targeting to privileged cloud access took less than three hours.

Microsoft cautioned that most of the targeting was unsuccessful, and that an affected application or successful sign-in does not by itself establish that data was accessed. ConnectWise said its existing backup archives showed no indication of compromise and that it suspended Cloud Backup, SaaS Security and Cloud Management while investigating. Separately, OpenAI said AI had identified critical PHP vulnerabilities that were patched October 21, and forecast that AI-found critical vulnerabilities would increase sharply in coming months.

Faster Attacks Raise the Response Stakes

The reports point to a practical change in the pace and scale of cyber operations. Automation can keep scanning, testing credentials or adapting scripts without the limits of a human operator’s working hours. Microsoft says agents can work around the clock; Palo Alto Networks’ Unit 42 described one agent performing hundreds of hours of manual targeting analysis in minutes. These are source characterizations, not evidence that every attack is more effective.

For organizations, the concern is the shrinking time available to spot and contain an intrusion. Microsoft’s account of access in under three hours makes slow identity reviews and delayed incident escalation harder to justify. The industrial-control advisory has a different consequence: exposed PLCs can connect cyber activity to physical operations. The agencies’ stated focus on preventing operational effects makes basic network isolation and monitoring relevant beyond IT teams.

AI also adds pressure on defenders. OpenAI’s report describes AI identifying flaws before attackers, but its forecast of a sharp rise in such discoveries is a prediction, not a measured trend. If more vulnerabilities are found and disclosed, organizations may face a heavier patching workload. Inventory, patch prioritization, phishing-resistant authentication and rehearsed response plans remain the practical measures identified in the source material; buying AI tools alone does not address the documented weaknesses.

Three Reports, Different Evidence

The August advisory concerns industrial control systems. The agencies say actors found exposed Siemens PLCs through internet-scanning services and used AI-generated exploitation scripts disguised as monitoring tools, built on the open-source snap7 library. The advisory recommends inventorying controllers, patching firmware, removing direct internet exposure, blocking TCP port 102 at the perimeter, separating IT and operational technology networks, and requiring multifactor authentication for remote OT access. It also recommends monitoring S7 traffic for writes outside approved change windows.

The Microsoft report concerns a trusted software supply chain and cloud identity, rather than direct manipulation of industrial equipment. Microsoft says ConnectWise first disclosed its compromise on October 16 and describes Storm-0940 as active since 2021. Its figures distinguish large-scale attempts from successful access: more than 151,000 logons failed, while privileged access occurred in several separate attacks. The report does not establish that every tenant targeted was compromised.

A third case cited by Unit 42 describes a Chinese-speaking actor using the DeepSeek model with the Hermes Agent framework and directing it through Telegram. The source account says the agent searched GitHub after its first exploit failed. Across these cases, the common thread is software assisting conventional reconnaissance and exploitation. A forecast from a security leader about a coming “vulnerability tsunami” and roughly 18 months to respond is an individual opinion, not an independently measured projection.

“This is not a theoretical risk—it is an active threat.”

— Joint advisory by the NSA, CISA, FBI, Department of Energy and EPA

What the Reports Do Not Establish

The available reporting does not establish how much data, if any, was accessed through the ConnectWise-related activity. Microsoft says an affected app or successful sign-in does not necessarily mean data was reached, while ConnectWise reported no indication of compromise in existing backup archives and said its services were suspended during its investigation. Those statements do not resolve every question about the scope or outcome of the incidents.

The agencies describe activity against PLCs and assess possible preparation for operational effects, but the source material does not report that the activity caused a disruption to critical infrastructure. It also does not quantify how many organizations were affected by the industrial-control activity. OpenAI’s projection about future vulnerability discoveries and the security leader’s warning about a coming surge remain forecasts. The underlying reports do not provide a single measure of whether AI has increased the overall success rate of cyberattacks.

Containment and Basic Defenses

ConnectWise’s services were suspended while its investigation proceeded; the source material does not give a final investigation result or a restoration timetable. Organizations that use affected services should follow provider updates and review application permissions and sign-in logs. Microsoft’s findings also support checking third-party application credentials and access to cloud tenants rather than treating an application’s trusted status as proof that activity is safe.

For industrial operators, the agencies’ recommended steps include checking every PLC’s internet exposure, applying firmware updates, blocking unnecessary network access and separating operational technology from corporate IT. For all organizations, the near-term work is to confirm asset inventories, set patch deadlines, strengthen remote access with phishing-resistant sign-in where available, review third-party apps and practise incident response. Users can begin with their email account, securing it with multifactor authentication and checking for unfamiliar sessions or recovery settings. Further details on investigation findings, affected systems and any confirmed operational or data impact remain the next facts to watch.

Key Questions

Did AI cause a confirmed disruption to industrial systems?

The joint agency advisory reports AI-generated scripts targeting Siemens PLCs and assesses that actors may be preparing for operational effects. The source material does not report a confirmed disruption caused by this activity.

Were all the more than 2,250 Microsoft-reported tenants compromised?

No. Microsoft said the actor attempted sign-ins to more than 2,250 tenants and that most targeting was unsuccessful. It also cautioned that a successful sign-in does not by itself prove data was accessed.

What should organizations do first?

Start with the controls named in the reports: inventory systems, patch known vulnerabilities, remove unnecessary internet exposure, strengthen remote authentication, review third-party application access and practise incident response.

Is a surge in AI-found vulnerabilities confirmed?

No. OpenAI reported AI-found critical PHP vulnerabilities that were patched October 21, and forecast that such findings would increase sharply. That statement is a forecast, not a confirmed count of future vulnerabilities.

Source: ThorstenMeyerAI.com