On this page

The banner is an AI-generated editorial illustration, not a diagram of verified infrastructure dependencies or attack paths.

The FBI issued a warning about an autonomous penetration-testing framework on November 13. By November 18, the service-disruption reports stretched across banking, cloud infrastructure, workplace software, aviation, Apple services, and government systems. People were putting the warning next to those outages and asking the obvious question: are these things connected? I understand why. When enough systems have a bad week at the same time, it is reasonable to wonder whether something larger is going on.

What I do not want to do is turn that reasonable question into an answer we have not established. An advisory about active intrusions and a statement about the cause of a particular outage are different things. Both can be accurate without contradicting each other, and the actual technical story here is interesting enough without adding connections the evidence does not support.

What the FBI warning actually says

The FBI’s November 13 FLASH advisory, numbered FLASH-20261113-001, concerns ARTEX, an LLM-driven penetration-testing framework being used maliciously. It describes campaigns observed since at least August 2026 across multiple sectors, with some intrusions reaching privileged access in less than three hours. This was a warning about activity already underway, not an announcement that attacks would begin on November 13.

ARTEX is not a single exploit or a magic key to every network. Cisco Talos describes an operator setting a target and objective, a planner dividing the work, and worker agents using security tools while sharing findings. That organization of the work matters: the operator does not have to manually shepherd every transition from one useful discovery to the next. The framework was built for authorized testing; its abuse does not make every deployment malicious.

I have spent enough time working with agents to recognize why that is useful, and why it becomes a problem in the wrong hands. The same ability to connect a discovery to a next step that helps an agent solve a development problem can help an attacker pursue an intrusion. That is not a claim that the software has developed criminal ambitions. There are people selecting the targets and supplying the objectives.

The dates matter, but they do not establish a connection

Here is a short chronology of the public record. These are publication dates, not a claim that the underlying events began on those dates.

That puts the advisory in context: the malicious activity was being investigated before this particular cluster of outages. An older warning does not rule out later attacks, but reposting it alongside a new disruption does not establish that the two share a cause either. For that, we need the incident records.

Which services actually failed?

The list is broader than aviation, and it deserves more than a collection of outage headlines. This is a selected inventory through the evening of November 18, 2026, U.S. Central time, not a complete worldwide outage census or a completed November 19 record. Clock times below are UTC; date ranges cover incidents crossing midnight. Where a source does not establish a common impact window, I have not invented one.

The tables scroll horizontally on narrow screens so the date column stays intact. Operator statements establish what the organization reported; they are not a substitute for an independently verified root-cause investigation.

Apple is a useful example of why I do not want a single duration pasted across a vendor’s entire product list. StatusGator recorded an approximately six-hour aggregate incident on November 17. Apple’s component records have different start and end times. Those are different measurements, not necessarily contradictory ones, and the next day’s Stocks entry belongs on its own line.

Smaller incidents are not global outages

The infrastructure providers have useful records too, provided we preserve their scope. A console failure, a configuration delay, a regional network path, and a failed message to one mobile carrier are not interchangeable observations.

Customer reports still need attribution to a failure

The banking example is particularly instructive. AP’s reporting says Bank of America and Citigroup were not experiencing their own banking-service problems; U.S. Bank described delays involving other institutions, and Zelle’s operator said its network remained operational. CBS also distinguishes complaints from operators’ statements. A customer unable to complete a transfer has a real problem, but that does not tell us which end of the transaction failed.

I have not counted the additional Gmail and Charles Schwab claims as confirmed independent outages here. The material reviewed did not establish sufficiently specific provider records for their scope, duration, and cause. That is a reason to keep investigating those leads, not to quietly promote them into facts because they make the list longer.

Shared dependencies are worth investigating without inventing a shared attacker

The Cloud Security Alliance’s November 18 research note examines this cluster through operational resilience and attribution. Its useful point is that mechanisms intended to improve resilience can also propagate a fault: failover, disaster recovery, and shared dependencies need their own failure analysis. The note does not establish that patches for AI-discovered vulnerabilities caused these particular outages. That hypothesis needs evidence too.

For this article, the strongest connections are the ones someone actually documented: Anthropic names Microsoft as the cause of its Microsoft 365 connector failure, and the banking statements explain how a Chase problem affected transactions involving other institutions. That is much better evidence than matching headlines. It still does not connect those two dependency chains to each other, to ARTEX, or to the FAA and NSA incidents.

There is an opposite mistake worth avoiding as well. Saying investigators have not identified compromise is not the same as completing a forensic investigation and excluding it. I want early statements to tell me what has been checked and what remains unknown, not replace one confident guess with another. The sources reviewed here do not establish that ARTEX caused this outage cluster or that it was one coordinated attack.

The ConnectWise connection is documented, and the numbers need care

There is a real supply-chain story here. In its October 21 investigation, Microsoft attributes the ConnectWise compromise to Storm-0940, a China-state-aligned actor, and describes ARTEX accelerating the abuse of compromised application identities. That is a documented trust relationship being abused, not a connection inferred from two organizations having trouble on the same afternoon.

The figure of more than 2,250 tenants refers to attempted sign-ins, not 2,250 confirmed breaches. Microsoft’s separate password-spray account records more than 151,000 failed sign-ins, peaking at 2,900 per minute, without observed successful authentication in that particular activity. Its account of subsequent application-credential abuse does describe successful access and follow-on activity in some environments. Combining those findings into a single claim that thousands of companies were breached would lose the distinction that makes the report useful.

Attempts, successful authentication, privileged persistence, and confirmed data theft are different observations. An investigation needs to establish which occurred, where, and in what sequence. Big numbers get attention, but I would rather know what the number actually counts.

This is broader than one tool or one attacker

Microsoft’s November 6 report describes Storm-3358, a financially motivated cluster, using ARTEX alongside conventional tools to exploit web applications and deploy remote-access software. That is a separate actor from Storm-0940. Shared tooling is not evidence that the operators share an objective, much less that every subsequent outage belongs to either campaign.

Censys’s investigation adds another useful perspective: exposed ARTEX consoles, other offensive tools on some of the same hosts, and open directories leaking operators’ own material. One exposed directory included an operator’s home directory, SSH files, and shell history. Apparently, putting an AI in the toolkit does not stop an operator from leaving their own files hanging out on the Internet. Censys also explicitly cautions that some exposed installations may belong to authorized testers; a console count is not an attacker count.

What worries me is not that scanners or stolen credentials suddenly exist. It is the reduced friction between finding something interesting and acting on it, repeatedly, across multiple targets. My reading of this research is that defenders need to shorten their own decision paths, not merely collect more alerts and hope someone eventually works through the queue.

What would persuade me that the outages were connected?

I would look for correlated intrusion evidence: a shared compromised supplier, matching application identities or stolen credentials, related infrastructure, and a sequence of unauthorized changes that explains the disruption. A common provider could also explain several outages without an attacker being involved. The dependency is a lead; the failure mechanism still needs investigating.

Even matching indicators need context. A shared address might belong to a proxy or hosting service used by unrelated operators, and the same public tool can appear in different campaigns. Useful attribution comes from corroborating observations, not treating one overlap as a verdict. I would want the organizations’ incident timelines, authentication records, configuration changes, and independent findings to agree well enough to support the proposed explanation.

I am quite happy to keep asking questions while those early statements are incomplete. What I cannot do is treat missing public detail as evidence for my preferred explanation. The calendar gives us a reason to investigate, not permission to fill in the blanks.

The practical problem is access, permissions, and response time

The Talos recommendations emphasize patching exposed systems, protecting credentials, limiting application privileges, correlating telemetry, and preparing for rapid containment. My practical test would be to ask which identities a compromised application could reach, what those identities can change, and who can shut down that access. If answering those questions takes longer than the intrusion itself, the response plan needs work.

The application identity deserves as much attention as the human account. Protecting a person’s login is important, but it does not automatically constrain a stolen application credential. In reviewing my own setup, I would inspect application grants and subsequent permission changes, not stop at checking whether users have MFA enabled.

For my own agent workflows, I want credentials kept out of prompts and casually readable project files, with each process receiving only what it needs. That is one reason I work on Secrets Kit, but I do not want to sell a credential store as a cure for compromised software. As our security documentation explains, a process receiving a secret can expose it. Local encryption protects stored material; it does not make a running process trustworthy or stop an agent with sufficient command access from inspecting its environment.

I would also rehearse revocation rather than assume changing one password ends the incident. The FBI’s documented persistence techniques include adding credentials to existing OAuth applications. Containment has to address what the attacker created as well as the credential that let them in, while preserving the evidence needed to understand what happened.

The FBI warning deserves attention on its own merits. Whether any of the November outages eventually turns out to share a cause is a separate investigation. We already have enough documented evidence to take agent-assisted intrusions seriously; we do not need to turn a bad week for the Internet into an attribution claim before the facts get there.

Research checked on the evening of November 18, 2026, U.S. Central time. Some provider records already carry November 19 UTC timestamps; that does not make this a completed November 19 incident survey. Sources include the original advisory, operator status records, researcher reports, and attributed company statements in contemporary reporting. This is an assessment of that public record, not a forensic investigation of the affected organizations. Status histories may be revised as investigations continue.