Blog
/
/
May 21, 2020

Securing AWS Cloud Environments

Discover how self-learning AI in AWS environments detects and beats threats early with enterprise-wide analysis.
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
Andrew Tsonchev
VP, Security & AI Strategy, Field CISO
Default blog image
21
May 2020

Cloud platforms transform the way we build digital infrastructure, allowing us to create incredibly innovative environments for business – but often, it’s at the cost of visibility and control.

With complex hybrid and multi-cloud infrastructures becoming an essential part of increasingly diverse digital estates, the journey to the cloud has fundamentally reshaped the traditional paradigm of the network perimeter, while expanding the attack surface at an alarming rate. Meanwhile, traditional security controls still only offer point solutions that rely on retrospective rules and threat signatures and fail to stop novel and advanced attacks.

To shoulder the weight of shared responsibility for cloud security, organizations require the approach offered by Darktrace DETECT & RESPOND. With Self-Learning AI, DETECT continuously learns what normal ‘patterns of life’ look like for every user, device, virtual machine, and container across an organization. By actively developing a bespoke understanding of ‘self,’ the DETECT can identify the subtle anomalies that point to an advanced attack, without any pre-defined assumptions of ‘good’ or ‘bad' and RESPOND can autonomously interfere to stop emerging threats without disrupting business operations.

As more and more businesses turn to AWS to leverage the benefits of cloud infrastructure, gaining visibility and security for AWS-hosted data and applications is absolutely crucial. The advent of AWS VPC traffic mirroring has allowed Darktrace to shine a light on blind spots in our customers’ AWS environments, ensuring that our Cyber AI security platform can stop any type of threat that emerges. With the AI-powered security securing your AWS environment, you can embrace all the benefits of the cloud with confidence.

Self-learning Cyber AI with granular, real-time visibility

VPC traffic mirroring gives our Self-Learning AI access to granular packet data, allowing DETECT to extract hundreds of features from the raw data and build rich behavioral models for our customers’ AWS cloud environments. This real-time visibility to the underlying fabric of AWS environments provided by VPC traffic mirroring helps Darktrace Cyber AI learn ‘on the job,’ continuously adapting as your business evolves. Darktrace provides the only security solution that learns in real time, a critical feature given the speed and scale of development in the cloud.

Unified control: Correlating patterns across infrastructure

Taking a fundamentally unique approach, DETECT actively correlates activity across AWS and beyond – whether your digital ecosystem includes other cloud environments, SaaS applications, or any range of on- and off-premise infrastructure. From a threat detection perspective, this is crucial, as security events detected in one part of an organization are often part of a broader security incident. This ensures that threats in the cloud are not siloed from monitoring of the rest of the infrastructure, nor are the implications for cloud security ignored when intrusions occur elsewhere in the network.

Neutralizing sophisticated and novel attacks

Legacy security controls miss novel and advanced attacks targeting cloud infrastructure. With VPC traffic mirroring supporting Darktrace Cyber AI’s understanding of an organization’s AWS environment, any slight changes from normal behavior that may indicate a potential threat can be detected immediately. This allows the DETECT to catch the full range of cloud-based attacks, from zero-day malware, to stealthy insider threats.

“Darktrace represents a new frontier in AI-based cyber defense. Our team now has complete real-time coverage across our SaaS applications and cloud containers.”

— CIO, City of Las Vegas

How it works: Using VPC traffic mirroring to analyze AWS traffic

For customers leveraging AWS within an IaaS model, Darktrace uses VPC traffic mirroring to collect metadata from mirrored VPC packets in a Darktrace probe known as a ‘vSensor’. The vSensor captures real-time traffic and selectively forwards relevant metadata to a Darktrace cloud instance or on-premise probe. From here, DETECT correlates VPC traffic with cloud, email, network, and SaaS traffic across a customer’s hybrid and multi-cloud infrastructure for analysis.

By utilizing VPC traffic mirroring in this way, the Immune System can perform deep packet inspection on traffic in the customer’s AWS cloud environment, up to and including the application layer. Hundreds of features are extracted from the raw data, ranging from high-level metrics of data flow quantities, to peer relationship meta-data, to specific application layer events. These features allow Darktrace Cyber AI to build rich behavioral models that let it understand normal patterns of life for the organization and detect malicious activity. It is important that Darktrace is able to construct these metrics from the raw data rather than relying on flow logs alone, as flow logs don't provide the required level of granularity or real-time events within connections.

For non-Nitro AWS instances, we deploy lightweight agents known as ‘OS-Sensors’ that feed relevant traffic to a local vSensor and, in turn, to a Darktrace cloud instance or on-premise probe. Once configured, OS-Sensors can easily be scaled as new instances are spun up. Darktrace also offers a specialized OS-Sensor that provides coverage in containerized systems like Docker and Kubernetes.

Richer context with AWS CloudTrail logs

In addition to analyzing data with VPC traffic mirroring, the DETECT also monitors management and data events within AWS. It does so via HTTP requests for logfiles generated by AWS CloudTrail, which monitors events from all AWS services, including:

  • EC2
  • IAM
  • S3
  • VPC
  • Lambda

Different event types produced via CloudTrail are organized by Darktrace into categories based on the action type and the AWS services that generate it. These different categories show up as metrics in the DETECT user interface, the Threat Visualizer. This information is used to provide even richer context in connection with mirrored traffic in VPCs, as well as all cloud, network, email, and SaaS traffic across a customer’s entire digital environment.

Darktrace deployment scenarios for AWS customers

For IaaS environments, Darktrace deploys a vSensor in each cloud environment. Within AWS environments, the vSensor captures real-time traffic with AWS VPC traffic mirroring. The receiving vSensor processes the data and feeds it back to the cloud-based Darktrace instance. AWS customers additionally have the option of deploying a ‘Darktrace Security Module’ to monitor IaaS management and data events at the API level, such as logins, editing virtual servers, or creating new access credentials.

Figure 1: A cloud-only deployment scenario — Darktrace manages a master cloud probe which receives traffic from sensors and connectors in IaaS and/or SaaS environments.

For hybrid IaaS deployments, Darktrace will similarly deploy vSensors, and OS-Sensors as appropriate. Cloud traffic and event data from AWS and any other cloud environments is then fed to a Darktrace probe in the cloud or on-premise network. For the latter scenario, Darktrace will deploy a physical appliance that ingests real-time network traffic via a SPAN port or network tap, allowing it to correlate patterns across the entire digital ecosystem.

Figure 2: A hybrid cloud deployment scenario, with multi-cloud infrastructure across AWS, Azure and GCP

For hybrid SaaS deployments, Darktrace will deploy provider-specific Darktrace Security Modules on either a physical or cloud-based Darktrace probe, in addition to any other relevant vSensors and OS-Sensors in place. SaaS data is then analyzed and correlated with traffic and user behaviors across AWS, other cloud environments, and any on- and off- premise cyber-physical infrastructure.

Figure 3: A hybrid SaaS deployment scenario

Defense against the full range of threats in the cloud

With the deep insight and powerful reaction capabilities of Cyber AI, Darktrace DETECT & RESPOND are the only proven technologies to stop the full range of cyber-threats in the cloud, including:

  • Critical misconfigurations
  • Insider threat
  • Compromised credentials
  • Novel and advanced malware
  • Password brute-force attacks
  • Data exfiltration
  • Lateral movement
  • Man-in-the-middle attacks
  • Crypto-jacking
  • Violations of policy

Case Studies

Crypto mining malware inadvertently installed

Darktrace detected a mistake from a junior DevOps engineer in a multinational organization with workloads across AWS and Azure and leveraging containerized systems like Docker and Kubernetes. The engineer accidentally downloaded an update that included a crypto miner, which led to an infection across multiple cloud production systems.

After the initial infection, the malware started beaconing out to an external command and control server, which was immediately picked up by Darktrace. With the external connection established and the attack mission instructions delivered, the crypto malware infection was then able to rapidly spread across the organization’s expansive cloud infrastructure at machine speed, infecting 20 cloud servers in under 15 seconds.

Extensive visibility into the organization’s AWS environment via VPC traffic mirroring was a key factor allowing Darktrace Cyber AI to identify the scale of the attack. With the dynamic and unified view across the company’s sprawling hybrid and multi-cloud infrastructure provided by Darktrace, the company’s security team was able to contain the attack within minutes, rather than hours or days. Even though the attack moved at machine speed, by leveraging solutions like VPC traffic mirroring to continuously analyze behavior in the cloud, Darktrace caught the threat at an early enough stage – well before the costs could start to mount.

Developer misuse of AWS cloud infrastructure

At an insurance group, a DevOps Engineer was attempting to build a parallel back-up infrastructure within AWS to replicate the organization’s data center production systems. The technical implementation was perfect, and the back-up systems were created – however, the cost of running the system would have been several million dollars per year.

The DevOps Engineer was unaware of the costs associated with the project and kept management in the dark. The cloud infrastructure was launched, and the costs started rising. Yet with real-time access to the company’s AWS environment provided by VPC traffic mirroring, Darktrace’s Cyber AI was immediately alerted to this unusual behavior, allowing the security team to take preventative action immediately.

With Darktrace Cyber AI, embrace the benefits of AWS

As organizations increasingly turn to the cloud and the threat surface continues to expand, security teams need self-learning AI on their side to gain the strongest insights, illuminate every blind spot, and stop all attacks.

By providing an enterprise-wide Cyber AI platform, Darktrace helps teams overcome the traditional security challenge of manually piecing together incidents across disparate corners of an organization. The unified visibility and control offered by Darktrace PREVENT, DETECT, RESPOND, & HEAL reduces the complexity and dashboard fatigue that many teams continue to struggle with, while the system’s multi-dimensional insight enhances its decision-making and threat confidence. Darktrace further augments this process with the Immune System’s AI Analyst capability, which takes the additional step of automatically investigating threats detected by Darktrace and producing concise, AI-generated reports that communicate the full scope of an incident.

With the granular, real-time visibility of VPC traffic mirroring Darktrace, you can be certain your AWS cloud environments are always protected.

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
Andrew Tsonchev
VP, Security & AI Strategy, Field CISO

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