Blog
/
AI
/
March 7, 2025

Darktrace's Early Detection of the Latest Ivanti Exploits

In January 2025, Ivanti disclosed two critical vulnerabilities affecting their products. Darktrace detected exploitation of these vulnerabilities as early as December 2024.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Hugh Turnbull
Cyber Analyst
Default blog image
07
Mar 2025

As reported in Darktrace’s 2024 Annual Threat Report, the exploitation of Common Vulnerabilities and Exposures (CVEs) in edge infrastructure has consistently been a significant concern across the threat landscape, with internet-facing assets remaining highly attractive to various threat actors.

Back in January 2024, the Darktrace Threat Research team investigated a surge of malicious activity from zero-day vulnerabilities such as those at the time on Ivanti Connect Secure (CS) and Ivanti Policy Secure (PS) appliances. These vulnerabilities were disclosed by Ivanti in January 2024 as CVE-2023-46805 (Authentication bypass vulnerability) and CVE-2024-21887 (Command injection vulnerability), where these two together allowed for unauthenticated, remote code execution (RCE) on vulnerable Ivanti systems.

What are the latest vulnerabilities in Ivanti products?

In early January 2025, two new vulnerabilities were disclosed in Ivanti CS and PS, as well as their Zero Trust Access (ZTA) gateway products.

  • CVE-2025-0282: A stack-based buffer overflow vulnerability. Successful exploitation could lead to unauthenticated remote code execution, allowing attackers to execute arbitrary code on the affected system [1]
  • CVE-2025-0283: When combined with CVE-2025-0282, this vulnerability could allow a local authenticated attacker to escalate privileges, gaining higher-level access on the affected system [1]

Ivanti also released a statement noting they are currently not aware of any exploitation of CVE-2025-0283 at the time of disclosure [1].

Darktrace coverage of Ivanti

The Darktrace Threat Research team investigated the new Ivanti vulnerabilities across their customer base and discovered suspicious activity on two customer networks. Indicators of Compromise (IoCs) potentially indicative of successful exploitation of CVE-2025-0282 were identified as early as December 2024, 11 days before they had been publicly disclosed by Ivanti.

Case 1: December 2024

Authentication with a Privileged Credential

Darktrace initially detected suspicious activity connected with the exploitation of CVE-2025-0282 on December 29, 2024, when a customer device was observed logging into the network via SMB using the credential “svc_negbackups”, before authenticating with the credential “svc_negba” via RDP.

This likely represented a threat actor attempting to identify vulnerabilities within the system or application and escalate their privileges from a basic user account to a more privileged one. Darktrace / NETWORK recognized that the credential “svc_negbackups” was new for this device and therefore deemed it suspicious.

Darktrace / NETWORK’s detection of the unusual use of a new credential.
Figure 1: Darktrace / NETWORK’s detection of the unusual use of a new credential.

Likely Malicious File Download

Shortly after authentication with the privileged credential, Darktrace observed the device performing an SMB write to the C$ share, where a likely malicious executable file, ‘DeElevate64.exe’ was detected. While this is a legitimate Windows file, it can be abused by malicious actors for Dynamic-Link Library (DLL) sideloading, where malicious files are transferred onto other devices before executing malware. There have been external reports indicating that threat actors have utilized this technique when exploiting the Ivanti vulnerabilities [2].

Darktrace’s detection the SMB write of the likely malicious file ‘DeElevate64.exe’ on December 29, 2024.
Figure 2: Darktrace’s detection the SMB write of the likely malicious file ‘DeElevate64.exe’ on December 29, 2024.

Shortly after, a high volume of SMB login failures using the credential “svc_counteract-ext” was observed, suggesting potential brute forcing activity. The suspicious nature of this activity triggered an Enhanced Monitoring model alert that was escalated to Darktrace’s Security Operations Center (SOC) for further investigation and prompt notification, as the customer was subscribed to the Security Operations Support service.  Enhanced Monitoring are high-fidelity models detect activities that are more likely to be indicative of compromise

Suspicious Scanning and Internal Reconnaissance

Darktrace then went on to observe the device carrying out network scanning activity as well as anomalous ITaskScheduler activity. Threat actors can exploit the task scheduler to facilitate the initial or recurring execution of malicious code by a trusted system process, often with elevated permissions. The same device was also seen carrying out uncommon WMI activity.

Darktrace’s detection of a suspicious network scan from the compromised device.
Figure 3: Darktrace’s detection of a suspicious network scan from the compromised device.

‍

Further information on the suspicious scanning activity retrieved by Cyber AI Analyst, including total number of connections and ports scanned.
Figure 4: Further information on the suspicious scanning activity retrieved by Cyber AI Analyst, including total number of connections and ports scanned.
Darktrace’s detection of a significant spike in WMI activity represented by DCE_RPC protocol request increases at the time, with little to no activity observed one week either side.
Figure 5: Darktrace’s detection of a significant spike in WMI activity represented by DCE_RPC protocol request increases at the time, with little to no activity observed one week either side.

Case 2: January 2025

Suspicious File Downloads

On January 13, 2025, Darktrace began to observe activity related to the exploitation of CVE-2025-0282  on the network of another customer, with one in particular device attempting to download likely malicious files.

Firstly, Darktrace observed the device making a GET request for the file “DeElevator64.dll” hosted on the IP 104.238.130[.]185. The device proceeded to download another file, this time “‘DeElevate64.exe”. from the same IP. This was followed by the download of “DeElevator64.dll”, similar to the case observed in December 2024. External reporting indicates that this DLL has been used by actors exploiting CVE-2025-0282 to sideload backdoor into infected systems [2]

Darktrace’s detection of the download of the suspicious file “DeElevator64.dll” on January 13, 2025.
Figure 6: Darktrace’s detection of the download of the suspicious file “DeElevator64.dll” on January 13, 2025.

‍Suspicious Internal Activity

Just like the previous case, on January 15, the same device was observed making numerous internal connections consistent with network scanning activity, as well as DCE-RPC requests.

Just a few minutes later, Darktrace again detected the use of a new administrative credential, observing the following details:

  • ‍domain=REDACTED hostname=DESKTOP-1JIMIV3 auth_successful=T result=success ntlm_version=2 .

The hostname observed by Darktrace, “DESKTOP-1JIMIV3,” has also been identified by other external vendors and was associated with a remote computer name seen accessing compromised accounts [2].

Darktrace also observed the device performing an SMB write of an additional file, “to.bat,” which may have represented another malicious file loaded from the DLL files that the device had downloaded earlier. It is possible this represented the threat actor attempting to deploy a remote scheduled task.

Darktrace’s detection of SMB Write of the suspicious file “to.bat”.
Figure 7: Darktrace’s detection of SMB Write of the suspicious file “to.bat”.

Further investigation revealed that the device was likely a Veeam server, with its MAC address indicating it was a VMware device. It also appeared that the Veeam server was capturing activities referenced from the hostname DESKTOP-1JIMIV3. This may be analogous to the remote computer name reported by external researchers as accessing accounts [2]. However, this activity might also suggest that while the same threat actor and tools could be involved, they may be targeting a different vulnerability in this instance.

Autonomous Response

In this case, the customer had Darktrace’s Autonomous Response capability enabled on their network. As a result, Darktrace was able to contain the compromise and shut down any ongoing suspicious connectivity by blocking internal connections and enforcing a “pattern of life” on the affected device. This action allows a device to make its usual connections while blocking any that deviate from expected behavior. These mitigative actions by Darktrace ensured that the compromise was promptly halted, preventing any further damage to the customer’s environment.

Darktrace's Autonomous Response capability actively mitigating the suspicious internal connectivity.
Figure 8: Darktrace's Autonomous Response capability actively mitigating the suspicious internal connectivity.

Conclusion

If the previous blog in January 2024 was a stark reminder of the threat posed by malicious actors exploiting Internet-facing assets, the recent activities surrounding CVE-2025-0282 and CVE-2025-0283 emphasize this even further.

Based on the telemetry available to Darktrace, a wide range of malicious activities were identified, including the malicious use of administrative credentials, the download of suspicious files, and network scanning in the cases investigated .

These activities included the download of suspicious files such as “DeElevate64.exe” and “DeElevator64.dll” potentially used by attackers to sideload backdoors into infected systems. The suspicious hostname DESKTOP-1JIMIV3 was also observed and appears to be associated with a remote computer name seen accessing compromised accounts. These activities are far from exhaustive, and many more will undoubtedly be uncovered as threat actors evolve.

Fortunately, Darktrace was able to swiftly detect and respond to suspicious network activity linked to the latest Ivanti vulnerabilities, sometimes even before these vulnerabilities were publicly disclosed.

Credit to: Nahisha Nobregas, Senior Cyber Analyst, Emma Foulger, Principle Cyber Analyst, Ryan Trail, Analyst Content Lead and the Darktrace Threat Research Team

Appendices

Darktrace Model Detections

Case 1

·      Anomalous Connection / Unusual Admin SMB Session

·      Anomalous File / EXE from Rare External Location

·      Anomalous File / Internal / Unusual SMB Script Write

·      Anomalous File / Multiple EXE from Rare External Locations

·      Anomalous File / Script from Rare External Location

·      Compliance / SMB Drive Write

·      Device / Multiple Lateral Movement Model Alerts

·      Device / Network Range Scan

·      Device / Network Scan

·      Device / New or Uncommon WMI Activity

·      Device / RDP Scan

·      Device / Suspicious Network Scan Activity

·      Device / Suspicious SMB Scanning Activity

·      User / New Admin Credentials on Client

·      User / New Admin Credentials on Server 

Case 2

·      Anomalous Connection / Unusual Admin SMB Session

·      Anomalous Connection / Unusual Admin RDP Session

·      Compliance / SMB Drive Write

·      Device / Multiple Lateral Movement Model Alerts

·      Device / SMB Lateral Movement

·      Device / Possible SMB/NTLM Brute Force

·      Device / Suspicious SMB Scanning Activity

·      Device / Network Scan

·      Device / RDP Scan

·      Device / Large Number of Model Alerts

·      Device / Anomalous ITaskScheduler Activity

·      Device / Suspicious Network Scan Activity

·      Device / New or Uncommon WMI Activity

List of IoCs Possible IoCs:

·      DeElevator64.dll

·      deelevator64.dll

·      DeElevate64.exe

·      deelevator64.dll

·      deelevate64.exe

·      to.bat

Mid-high confidence IoCs:

-       104.238.130[.]185

-       http://104.238.130[.]185/DeElevate64.exe

-       http://104.238.130[.]185/DeElevator64.dll

-       DESKTOP-1JIMIV3

References:

1.     https://www.ivanti.com/blog/security-update-ivanti-connect-secure-policy-secure-and-neurons-for-zta-gateways

2.     https://unit42.paloaltonetworks.com/threat-brief-ivanti-cve-2025-0282-cve-2025-0283/

3.     https://www.proofpoint.com/uk/blog/identity-threat-defense/privilege-escalation-attack#:~:text=In%20this%20approach%2C%20attackers%20exploit,handing%20over%20their%20login%20credentials

Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
Written by
Hugh Turnbull
Cyber Analyst

More in this series

No items found.

Blog

/

AI

/

November 19, 2026

Microsoft Perception, Agentic Insiders and the Role of Behavioral Security

Default blog imageDefault blog image

This week at Ignite, Microsoft announced that Microsoft Perception is generally available. It is a significant milestone for the industry, and one we welcome as a Microsoft partner. Microsoft is putting an architectural bet at the center of its security strategy: AI has changed the speed of cyber, and defense must change with it.

At Darktrace, we’ve long held the same view, so it’s encouraging to see a partner of Microsoft’s scale articulate it so clearly and bring it to market.

Security gets a team of agents

Perception is Microsoft’s agentic security system. It orchestrates red, blue, and green team agents through playbooks in a closed loop: red agents simulate attacks, blue agents detect, triage and investigate, and green agents fix and remediate. Rather than adding another assistant to the SOC, it creates coordinated teams of agents that share context. Security teams set the guardrails and approve high-impact actions.

Microsoft frames this as a three-layer cyber stack: signals, sensors and actuators; a context layer; and agents, harness and models on top. Together with partner sources, the foundation produces more than 165 trillion signals per day.  

The announcement also makes a second point that matters just as much. Microsoft is treating AI agents themselves as a new insider-risk category. In its words, “Agents are the new insiders.” They work at machine speed, around the clock, with broad access to data, apps, tools and other agents, and like any insider they can make mistakes, be manipulated or be compromised. New capabilities such as Dynamic Agent Risk (now in preview) and dynamic Conditional Access controls are designed to assess and contain that risk as it changes.

Four truths about security in the agentic era

The announcement is built on four ideas, and together they describe the new reality security teams are defending:

  1. Static security can’t keep up. Microsoft validates what many security practitioners have observed; the window between a vulnerability’s discovery and its exploitation is collapsing from months to minutes. Manual triage can’t answer that pace. Autonomous detection and response is now a requirement, not simply a “nice to have”.
  2. Agents must be treated as insiders. The question for security teams is no longer only “who is this user?” but “what is this agent actually doing?” Identity tells you who an agent is. Policy tells you what it is allowed to do. Neither tells you whether its behavior is normal.
  3. Security is moving from signatures to behavior and context. Dynamic Agent Risk looks across identity, data, endpoint, cloud and network signals and asks whether an agent’s actions are drifting from the intent of its task. That is behavioral thinking, and it is philosophically close to the Adaptive AI approach Darktrace has pioneered.
  4. Machine-speed attacks demand machine-speed response. Humans set the objectives and guardrails. Autonomous systems do the work inside them, both detecting and acting. Microsoft’s design has agents investigate, recommend and, within approved boundaries, act, with security teams setting the limits. At this pace, the gap between knowing something is wrong and doing something about it has to close to seconds.

The opportunity: where control plane meets behavioral context

Perception is an extraordinary control plane for agentic security. The question for security leaders is how to make it even more effective in the environments they actually run.

Real enterprises are heterogeneous. They run AWS and Google Cloud alongside Azure, and OT, IoT and third-party identity alongside Entra. Increasingly they also run AI agents and MCP-connected systems that no single vendor’s telemetry fully covers. Microsoft’s architecture recognizes this, with more than 500 connectors into the wider ecosystem.

That is where Darktrace’s role is distinct. The challenge isn’t signal volume, where Microsoft’s scale is unmatched. It’s deeply understanding what is normal for a specific organization, across every system, identity and agent in it. Together, we deliver two complementary layers:

  • Microsoft brings global intelligence and orchestration. It tells you what is known, what it means and what to do about it.
  • Darktrace brings organization-specific behavioral context. It tells you what is unusual here, right now, across the organizations AI, people and infrastructure, even if it has never been seen before.

The difference shows up in the numbers. A large enterprise generates billions of signals. Darktrace turns them into thousands of incidents, narrows those to hundreds of AI-led investigations, and surfaces as few as 20 that merit a human’s attention. For an agentic SOC, that kind of evaluated, prioritized input makes agents faster, not busier.

As enterprises deploy more agents, the hard problem becomes behavior that is technically permitted but unusual, manipulated or inconsistent with the agent’s purpose. Consider an agent that normally reads Salesforce records during US business hours and suddenly starts enumerating SharePoint and opening unusual outbound connections. Each step may use valid access and approved tools, so identity and policy checks can all pass. Spotting it requires knowing the behavior is abnormal for this agent, in this environment, right now.

That is why one principle in Microsoft’s AI Transparency Initiative matters so much: organizations should be able to see what their AI accesses and does, and independently verify those actions.  

  • Identity and permissions answer “should this agent be allowed to do this?”
  • Behavioral defense answers “even though it is allowed, is what it’s doing normal?”

Deterministic controls around non-deterministic AI are the right foundation, and continuously learned baselines are how organizations can verify those controls are working. ‍

What to look for in an agentic SOC architecture

As organizations adopt platforms like Perception, we’d encourage them to look for three capabilities:

  1. Behavioral context in the control plane. Agents work best with high-confidence signals rather than thousands of raw alerts: here is the behavior that materially deviates from this organization’s learned normal.
  2. ‍Behavioral reasoning on demand. During an investigation, agents should be able to ask what changed around a given identity, device or agent in the last 24 hours, and get a clear answer. ‍
  3. Autonomous, coordinated response across the stack. Response should be as fast as the threat without being reckless: acting immediately when confidence is high, constraining or reversing actions when it isn’t, and keeping a human in the loop when it matters. Within policy and human-approval guardrails, it should target the abnormal behavior rather than the whole business process and span identity, endpoint and the wider environment.

These are the areas where we’re focused, and where we look forward to working with Microsoft and the broader ecosystem.

Response is where speed is won or lost

In the AI era, detection and investigation only matter if action follows quickly. Perception brings agentic orchestration to that problem, with security teams setting the guardrails and approving high-impact steps. Autonomous response from Darktrace takes a complementary approach: it responds on behavioral deviation, in a way that is proportionate and targeted. It can interrupt activity that is abnormal for that specific device, identity or agent while leaving normal business activity running.

The two approaches fit together naturally. Behavioral signals can tell an orchestration layer that something has changed and how confident the system is. Orchestrated playbooks can then coordinate wider containment across identity, endpoint and cloud, within the policies customers define.

The bigger picture

The industry’s architecture is converging on identity, policy, telemetry, behavior, autonomous reasoning and machine-speed response. Microsoft is building formidable pieces of that picture, especially identity, policy, telemetry and orchestration.

Behavior is the layer Darktrace is built to provide: an independent intelligence that continuously learns how humans, machines and AI agents normally act, detects the moment reality departs from intent, and can respond to that deviation in a targeted, proportionate way that keeps normal business running. When attacks move at machine speed, understanding what is abnormal and acting on it quickly have to go together.

Perception brings together what Microsoft knows and orchestrates the response across its stack. Darktrace helps organizations understand what is normal for them and act on what isn’t. Customers building their agentic security strategy will need both.

Congratulations to our partners at Microsoft on this milestone. We look forward to helping customers secure the agentic era together.

Learn more about Darktrace Behavioral Defense.

Continue reading
About the author
Kellie Regan
Director, Product Marketing - Cloud Security

Blog

/

AI

/

November 19, 2026

Agentic attacks in the wild: Inside three ARTEX investigations

Default blog imageDefault blog image

Key insights

·       Darktrace observed activity in several customer environments involving infrastructure and behaviors associated with reported ARTEX-enabled campaigns, including activity linked to China-nexus espionage and financially motivated attacks.

·       In the higher-confidence cases, known infrastructure appeared alongside beaconing, unusual TLS, reconnaissance, tunneling, script retrieval, SMB activity and external data transfer. One Azure case had no observed network command and control at all, only key listing and application identity activity.

·       ARTEX is now used by actors with different objectives. Identifying the framework can help locate relevant activity, while the behavior around the affected system provides the stronger evidence for understanding compromise and attribution.

‍

Introduction

Attackers have moved beyond using AI for phishing and are running agentic frameworks; open-source tools like ARTEX, CAIRN, PentAGI and Hexstrike that let AI agents scan, exploit and move through an environment with little human input [1]. ARTEX has moved quickly from an offensive security project into live intrusion activity. Since at least August 2026, the framework has been associated with espionage, financially motivated attacks and opportunistic campaigns across government, financial services, technology, defense, telecommunications and other sectors. The FBI has documented ARTEX activity spanning reconnaissance, exploitation, credential abuse, lateral movement, collection, command and control, and exfiltration [2].

Darktrace has observed activity in customer environments that overlaps with infrastructure, tooling and behaviors reported in several of these campaigns. The cases below highlight how those intrusions appeared on the network, including the activity visible before an analyst can determine which actor or framework may be responsible.

ARTEX as part of the attacker workflow

ARTEX is an open-source, multi-agent offensive security platform that converts high-level objectives into actions carried out by specialized agents [2]. Operators have used it to automate activity across the attack lifecycle, including scanning, exploitation, credential activity and post-compromise operations. Some reported intrusions moved from initial targeting to privileged access in under three hours [2].

The framework is now associated with actors pursuing different objectives and using different post-exploitation tooling. The original public repository was removed in October 2026, but archived copies and localized versions remain available. For defenders, ARTEX is more useful as context for an investigation than as an attribution shortcut.

Darktrace observations show the same point at network level. Infrastructure linked to reported ARTEX campaigns appeared alongside beaconing, tunneling, unusual TLS, reconnaissance, file retrieval and lateral activity.

Case 1: Espionage-linked activity

Darktrace observed activity associated with BLOODALCHEMY command-and-control (C2) infrastructure in two customer environments. In one environment, five devices communicated with nginxmysql[.]com and 45.153.126[.]223 between October 23 and November 2. Both indicators had previously been linked to China-nexus espionage activity involving ARTEX [4].

The connections were accompanied by suspicious beaconing, repeated successful connections and unusual self-signed TLS. One system began making suspicious TLS connections to nginxmysql[.]com on October 23. Beaconing followed on October 24, and SMB scanning appeared later in the sequence. Other affected systems subsequently communicated with previously unseen external endpoints.

Prior to the observed C2, Darktrace detected curl requests retrieving executable and script content including /systemd, /wazuh, linux_amd64, u.sh and q.sh. Related telemetry included DRSGetNCChanges activity consistent with DCSync, LDAP enumeration, DNS zone transfers, network scanning, certificate downloads and SMB writes involving start.bat.

Figure 1: Autonomous Response model alert in due to the identification of multiple underlying lateral movement related activities, including spikes in SMB and RPC operations on an affected Ivanti network device during an Artex-supported Vapor Panda intrusion.
Figure 2: Autonomous Response action summary console listing all recommended actions for an affected Ivanti network device following the detection of several underlying anomalous behaviors during the Artex-supported Vapor Panda intrusion.

BLOODALCHEMY has been reported in more than one China-nexus cluster [5]. SoftEther infrastructure observed in one environment provided another point of correlation with reported VAPOR PANDA tradecraft. The moderate-confidence assessment tying this to a Chinese nexus threat actor is based on infrastructure, victim context, tradecraft behavior that followed the initial connection, and public reporting.

Case 2: Financial-sector activity

In early November, Darktrace observed activity in two financial-sector environments that overlap with reported ARTEX infrastructure. On November 5, a server connected to 213.111.150[.]145:8099 and downloaded wisp-agent, associated with WISP C2 activity.

In a second environment, a device attempted connections to 85.11.167[.]52 on November 1 and 2. The connections occurred alongside beaconing to new and rare destinations, anomalous TLS, possible tunneling and unusual package downloads.

The device also communicated with temp[.]sh, ssh.localhost[.]run, localhost[.]run, termbin[.]com, pastebin[.]com and GitHub-hosted release infrastructure. The sequence showed potential tooling retrieval, C2, tunneling and use of external services capable of staging or moving data.

Case 3: Credential collection in Azure

On October 20, Darktrace observed a sweep of credential collection in a customer’s Azure environment that is consistent with ARTEX use. The intrusion began with connections to the virtual network from 43.98.196[.]73 (Alibaba Cloud). Open-source scanning data associates the address with ARTEX.

A compromised user identity made requests to the Azure Resource Manager API, though how it was compromised is unknown. The requests listed keys and secrets across API Management, web and function apps, Cognitive Services, Event Hubs, storage accounts and a managed Kubernetes cluster. With those credentials the attacker compromised multiple application identities. The attacker then used the application identities and the user identity to retrieve more credentials, change firewall and security rules and run scripts on virtual machines. Microsoft Defender alerts showed attempted execution of scripts related to Mimikatz and Impacket.

In a cloud environment, such privileged and enumerative operations are potentially indistinguishable from legitimate administrative actions. Consequently, the sequence and context of such operations signified more than any specific API call. There was no C2 traffic to match, and listing keys and using application identities are also what administrators and automation do. A compromised user, credential retrieval across several Azure services, new application identities, more credential collection and changes to security controls only made sense together, and by then access was spreading through the cloud environment.

Figure 3: Darktrace Advanced Search showing Azure AD operation names associated with the activity.
Figure 4: Darktrace Advanced Search showing the Azure Resource Manager action used to execute scripts.
Figure 5: Darktrace Device Event log window showing the triggered models related to the suspicious Azure activity.
Figure 6: Autonomous Response model alert for affected Azure account during Artex intrusion due to the  unusual source IP for the noted activity and the unexpected privileged operations in the Azure environment.
Figure 7: Autonomous Response action summary console for hijacked cloud Azure Identity following the detection of anomalous SaaS/IaaS actions including key/secret requests and Firewall configuration changes.

‍

Shared tooling weakens attribution signals

The three cases looked different on the network: BLOODALCHEMY infrastructure and espionage-consistent tradecraft, WISP infrastructure in financial-sector systems, and Azure identity and control-plane activity with no C2 at all.

Shared tooling has complicated attribution for years, and ARTEX adds to it because the framework carries out more of the attack, so reconnaissance, exploitation attempts and some post-compromise activity can look the same whoever set the objective. Attribution still needs infrastructure, malware, victimology, timing and the sequence of behavior inside the environment, and an ARTEX link is one input to that. Moreover, the behavior and the agent will still be shaped by the biases, preferences, and tradecraft of its operators.

At its core, ARTEX’s planner and worker agents identify and record facts, while exploring intents. However, the way the Large Language Model (LLM) chooses its next steps toward an objective is shaped fundamentally by the skills and tools available in its context. This includes its starting context, as well as various possible Model Context Protocol (MCP) plugins and user-injected context (e.g. user input mid-operation). Operators still have preferred tradecraft, and this preference shapes the pathways the harness will provide to the LLM in context prompts. Even on the same platform, customization based on operator preferences and goals will remain a key facet of campaign and actor identification.

Detection and response

Across the Darktrace cases, the stronger signals came from behavior after the connection: beaconing, abnormal TLS, reconnaissance, unusual authentication, tunneling, script retrieval, SMB activity and outbound transfer. Automated activity also produced compressed bursts of requests, sequential enumeration and repeated attempts with small changes.

With agentic tools reaching privileged access in under three hours, analysts may have only a short window to connect scanning or authentication activity to credential changes, new administrative access, tooling retrieval or lateral movement. Keeping network, identity and cloud telemetry together shows what happened before and after the first match, and whether a connection was noise or an intrusion moving toward privileged access.

In some of these cases, Darktrace's Autonomous Response took or recommended action against the activity, including blocking internal connectivity over specified ports, inhibiting outbound connections with likely C2 endpoints, and/or disabling SaaS/IaaS user accounts. While many of these recommended actions required human confirmation due to deployment configuration preferences, had these actions been applied autonomously at the time of alert, the scope of activity would have been limited, thereby giving analysts time to investigate and respond.

ARTEX won’t be the last of these frameworks. The next ones will come with new capabilities and defaults, but an intrusion still must interact with the target environment, and that shows up in how systems, identities and applications behave even after the indicator has aged out. The harder intrusions to catch will have no infrastructure to match, just ordinary API calls and legitimate identities. Detecting those depends on knowing what normal looks like for each identity and device. Containing abnormal activity at machine speed can stop an intrusion progressing while analysts establish impact and its extent. Autonomous Response does not replace that human analysis, but rather augments defender teams' capabilities by extending the window for investigation.

‍

Credit to Nathaniel Jones (SVP, Global Threat Intelligence), Eugene Chua (Principal Analyst), Sam Lister (Senior Security Researcher), Adam Potter (Associate Principal Cyber Analyst), Daniel Levy (Threat Hunting Data Scientist)

Edited by Ryan Traill (Content Manager)

Appendices

Darktrace model detections

·       Anomalous Connection / Multiple HTTP POSTs to Rare Hostname

·       Anomalous Connection / Rare External SSL Self-Signed

·       Anomalous Connection / Suspicious Self-Signed SSL

·       Compromise / Large Number of Suspicious Successful Connections

·       Compromise / Suspicious Beaconing Behaviour

·       Compromise / Agent Beacon to New Endpoint

·       Compromise / Beacon to Young Endpoint

·       Compromise / SSL Beaconing to Rare Destination

·       Compromise / Suspicious TLS Beaconing To Rare External

·       Compromise / Possible Tunnelling to Bin Services

·       Device / Anomalous Github Download

·       Device / Anomalous Package Download

·       Device / Initial Attack Chain Activity

Indicators of compromise (IoCs)

nginxmysql[.]com

45.153.126[.]223

213.111.150[.]145

wisp-agent

85.11.167[.]52

43.98.196[.]73

192.121.47[.]20

www[.]ddduuuppp[.]com

89.46.234[.]50

sqlserver-sqlite[.]com

199.19.95[.]66

graphics-hook-filter64.dll

graphics-hook_config.bin

References

1.      Google. GTIG AI Threat Tracker - https://cloud.google.com/blog/topics/threat-intelligence/agentic-threat-activity-crosses-a-significant-threshold

2.      Federal Bureau of Investigation, Threat Overview of ARTEX Autonomous Penetration Testing Framework, FLASH-20261113-001, 13 November 2026: https://www.ic3.gov/CSA/2026/261113.pdf

3.      Microsoft Security Blog, Storm-0940 Uses ARTEX Agentic AI in ConnectWise Supply Chain Compromise: https://www.microsoft.com/en-us/security/blog/2026/10/21/storm-0940-uses-artex-agentic-ai-connectwise-supply-chain-compromise/

4.      CrowdStrike, VAPOR PANDA Uses ARTEX to Scale Global Campaign: https://www.crowdstrike.com/en-us/blog/vapor-panda-uses-artex-to-scale-global-campaign/

5.      Bitdefender, SilkParasite: Tracking a China-Nexus APT Across Central Asia: https://www.bitdefender.com/en-us/blog/businessinsights/silkparasite-tracking-china-nexus-apt-across-central-asia

‍

‍

Continue reading
About the author
Nathaniel Jones
SVP, Global Threat Intelligence
Your data. Our AI.
Elevate your network security with Darktrace AI