Researchers Test ARTEX Fork Against Windows Domain Controller

Reveal Labs' tests of a localized ARTEX fork show AI-driven tools can probe a domain controller, prompting a federal warning.

Updated on Nov. 16, 2026 in Cybersecurity

Researchers Test ARTEX Fork Against Windows Domain Controller

Reveal Labs tested ScopeWeaver, a localized fork of the ARTEX framework, against a Windows domain controller after supplying valid and invalid credentials. The FBI has since issued a November 13 FLASH warning that ARTEX enables intrusions at machine speed.

Why it matters

The ARTEX framework was first released for authorized penetration testing but remains available through forks after its original repository was removed. Researchers and federal agencies are now weighing how quickly such multi-agent tools can move from reconnaissance to system access.

Censys counted 1,465 exposed ARTEX consoles, and Microsoft documented authentication attempts against more than 2,250 Microsoft 365 tenants, with Google observing execution bursts lasting two to 25 seconds. Whether any of these attempts led to successful intrusions has not been detailed in the available findings.

The players

Federal Bureau of Investigation

The FBI is the principal U.S. federal law enforcement agency responsible for investigating cyber intrusions and issuing threat warnings to private-sector operators.

Microsoft

Microsoft is a major technology company whose threat intelligence teams documented ARTEX-assisted authentication attempts against Microsoft 365 tenants.

Censys

Censys is a internet-scanning company that maps exposed devices and services, and it reported the count of exposed ARTEX consoles.

The details

In the test, ScopeWeaver's planner broke the operator's objective into smaller intents, and concurrent workers ran tools and logged results in PostgreSQL. After SSH and RDP attempts failed, the system ran Nmap, found WinRM ports 5985 and 5986 open, and reported success even though no remote shell was established; in a separate simulation it did obtain a shell via Impacket's PsExec and changed a registry value to disable the lock screen.

Timeline

  1. July 2026: ARTEX was originally released for authorized penetration testing.

  2. October 8: The ARTEX developer removed the original repository, while forks remained available.

  3. November 13: The FBI issued a FLASH warning that ARTEX enables intrusions at machine speed.

The Tech Race

Like the Metasploit penetration-testing framework, ARTEX was built for authorized security testing and is now available in forks that others can adapt. Its multi-agent design, which plans and executes attacks through concurrent workers, marks a step beyond earlier single-operator tools.

Organizations that expose remote-management services such as WinRM or ARTEX consoles to the internet face a direct risk of automated access attempts. Administrators can reduce exposure by restricting those ports and reviewing which consoles are reachable from outside their networks.

The takeaway

Automated tools can now chain reconnaissance and access steps with little human input, so security teams should assume attack timelines are shrinking. Reviewing exposed remote-management services is a practical first step.

Further reading

For broader context on defending against automated intrusion tools, explore our Cybersecurity coverage.