A defense contractor does not have to be the first target to become part of a cyberattack. Sometimes the opening is a software provider with permission to enter a customer’s systems. That permission can be valuable to an intruder, particularly when the customer does not know exactly what the provider can reach.

On November 13, the FBI warned that attackers have been using ARTEX, an AI-assisted penetration-testing framework, to speed up intrusions. In some documented cases, attackers went from initial targeting to privileged access in less than three hours. That is a narrow window for identifying suspicious activity, contacting a vendor, and deciding which systems need to be isolated.

How Did Attackers Use ARTEX in the ConnectWise Cloud Backup Incident? 

The warning draws on an October incident involving ConnectWise Cloud Backup. According to Microsoft’s investigation, attackers obtained control of credentials associated with ConnectWise cloud applications and used ARTEX to attempt sign-ins to more than 2,250 customer tenants. Microsoft observed follow-on activity in some environments, including changes to application credentials and permissions. The 2,250 figure describes the reach of the attempts, not 2,250 successful breaches.

This is why supplier access deserves attention from people well beyond the IT department. A third-party application may have standing permission to administer cloud resources, read directories or handle data. Compromise that application, and the attacker may inherit an access path the customer already approved. A network perimeter can look perfectly respectable while an authorized connection is being misused.

For a Navy program or defense contractor, the practical concern is not a headline about a new hacking tool. It is whether a provider supports ship maintenance records, logistics applications, software development or another service whose availability matters to the work. If that provider’s credentials are stolen, the customer may have to suspend the connection, examine account activity and determine whether information was accessed or changed. Those are plausible consequences of this type of intrusion, not reported effects of ARTEX against a particular Navy program.

How Fast Can AI-Assisted Attacks Like ARTEX Reach Privileged Access? 

ARTEX did not invent password theft, weak application permissions or neglected portals. It helps attackers test those weaknesses quickly and in parallel. The FBI describes activity against supplier portals, legacy applications, cloud systems and third-party integrations, including the kinds of systems that receive less scrutiny than a company’s flagship network.

For defenders, the clock starts before a complete picture is available. Who approved the supplier’s access? What can the application do? Was a new credential added? Could the attacker still enter by another route? Those questions are harder to answer during an incident if the organization has never recorded the permissions and dependencies in the first place.

An organization also needs to distinguish suspicious access from confirmed data loss. Microsoft cautioned that an affected application, or even a successful authentication, does not automatically establish that information was stolen. Investigators need records of sign-ins, application changes, directory activity and resource access to make that determination.

Why Doesn’t Patching End a Supplier Compromise? 

One of the more troubling details in Microsoft’s account is the possibility of attackers adding credentials to an application and keeping access after the original problem is addressed. Rotating one password or disabling one connection may be necessary, but it does not prove the rest of the environment is clean.

That distinction should shape how government customers manage suppliers. It is reasonable to ask whether a vulnerability has been reported and whether a patch exists. It is more useful to ask whether the patch was installed, whether permissions were reduced, whether unauthorized credentials were removed and what evidence supports closing the finding.

The FBI recommends inventorying internet-facing applications, restricting administrative services, examining cloud permissions and preserving authentication records. Microsoft also advises customers to review tenants where the affected ConnectWise applications were previously authorized, even when an integration is no longer being used. In an active investigation, evidence must be preserved before irreversible changes are made.

What Should Defense Contractors Ask Suppliers After the FBI ARTEX Warning? 

Start with the access already granted. Identify which suppliers can reach important applications and cloud environments. Record the permissions, the business reason for them and the person accountable for approving them. Then look for standing privileges that are no longer needed.

Next, make remediation an outcome rather than a status update. Assign the finding, set a deadline, examine the corrective action and retain evidence that it worked. Where a compromise is suspected, involve qualified incident responders to assess whether additional accounts, permissions or persistent access remain.

Fortress Information Security helps organizations understand supplier dependencies, monitor exposure and track corrective actions through verification. That is useful work long before a breach. During an incident, a current picture of supplier access and remediation responsibility gives investigators and program leaders a better starting point.

The lesson from the FBI advisory is not that every supplier connection is dangerous or that every ARTEX attempt succeeds. It is that approved access can be exploited quickly, and an organization cannot contain what it cannot identify. The question worth taking to the next supplier review is simple: If this provider’s credentials were stolen tonight, could we show which systems it could reach, what activity occurred and whether its access had truly been removed?