AI-powered cyberattacks drive fears of a turbulent cybersecurity period
Hackers are using artificial intelligence to automate attacks faster than many security teams can respond, while researchers have uncovered serious flaws in widely used software and users report unexpected charges tied to stolen AI credentials.
Hackers are increasingly using artificial intelligence to automate cyberattacks at speeds that leave security teams struggling to keep up. Some cybersecurity professionals have begun calling the current wave of incidents "Black October," a label describing a series of emergencies rather than a single coordinated campaign. The concern is that the consequences can reach far beyond large corporations and into the personal accounts of ordinary users.
The central worry is speed. Traditionally, attackers needed considerable time and technical skill to investigate targets, develop methods of entry and analyze what they found. AI tools can now automate much of that work, operating continuously and pursuing several potential targets at once. As a result, companies may have less time to respond once criminals find a way into their systems.
Microsoft Threat Intelligence offered one of the clearest examples on Oct. 21, when it reported that a China-state-aligned hacking group, Storm-0940, had used an AI-powered penetration testing framework called ARTEX. The open-source tool can automate security testing tasks, including mapping networks and identifying potential weaknesses. In criminal hands, those same capabilities can accelerate attempts at unauthorized access. According to Microsoft, the group targeted hundreds of organizations across multiple industries, and several attacks resulted in unauthorized privileged access to cloud systems. In multiple cases, attackers reached that level of access in less than three hours.
Many of the attempts failed, but the scale of the activity is striking. Between Oct. 10 and 14, Microsoft recorded more than 151,000 failed login attempts in one campaign targeting 327 accounts across eight organizations. At its peak on Oct. 11, attackers generated roughly 2,900 failed login attempts per minute. The technique, known as password spraying, involves trying passwords against many accounts to find one that works. Microsoft said it did not observe successful logins in that specific campaign, but it documented unauthorized access and suspicious activity in other environments linked to the same threat group.
Microsoft also connected Storm-0940 to a compromise involving ConnectWise, a company whose software is used by IT service providers. Attackers exploited access associated with ConnectWise cloud applications to try to enter customer environments, and some carried out further activity through Microsoft cloud services, including changes that could help them maintain access. Microsoft cautioned that suspicious access does not automatically mean customer information was stolen. Even so, the episode shows how quickly AI can help attackers move once they obtain usable credentials.
The risk becomes personal in the experience of startup founder Colin Parsons, who woke up to roughly 50 billing notifications he did not expect. He reported that his OpenAI and Anthropic accounts had racked up $449 in charges he did not recognize, including $281 in unexpected OpenAI usage and $168 involving Anthropic. Both credentials were associated with OpenCode, an AI coding platform he had used.
On Oct. 17, OpenCode disclosed a security incident involving its Console service. The company said unauthorized access to a legacy system may have exposed third-party AI provider keys stored by some users, and it reportedly notified affected customers and advised them to revoke their credentials. OpenCode said the incident affected approximately 1.4% of its Console users who had connected external AI providers. The disclosure concerned credentials stored in Console rather than keys stored locally in OpenCode's desktop or command-line applications. Other users also reported unexpected charges, although those amounts have not been independently verified. OpenCode linked the incident to a large-scale AI model distillation attack but has not publicly established exactly how the reported unauthorized usage occurred.
The underlying message for users is straightforward. A working API key can allow someone to run paid services at the account holder's expense, which is why unexpected billing notifications can be an early warning sign. Security professionals generally advise users to review billing statements regularly, rotate credentials after any provider disclosure and avoid storing keys where they may be exposed. Researchers have also pointed to serious weaknesses in software that powers millions of websites, adding to the sense that the current period demands closer attention from organizations and individuals alike.
7
