Blog
/
Network
/
March 19, 2024

Pikabot Malware: Insights, Impact, & Attack Analysis

Learn about Pikabot malware and its rapid evolution in the wild, impacting organizations and how to defend against this growing threat.
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
Brianna Luong (Leddy)
Sr. Technical Alliances Manager
Default blog image
19
Mar 2024

How does Loader Malware work?

Throughout 2023, the Darktrace Threat Research team identified and investigated multiple strains of loader malware affecting customers across its fleet. These malicious programs typically serve as a gateway for threat actors to gain initial access to an organization’s network, paving the way for subsequent attacks, including additional malware infections or disruptive ransomware attacks.

How to defend against loader malware

The prevalence of such initial access threats highlights the need for organizations to defend against multi-phase compromises, where modular malware swiftly progresses from one stage of an attack to the next. One notable example observed in 2023 was Pikabot, a versatile loader malware used for initial access and often accompanied by secondary compromises like Cobalt Strike and Black Basta ransomware.

While Darktrace initially investigated multiple instances of campaign-like activity associated with Pikabot during the summer of 2023, a new campaign emerged in October which was observed targeting a Darktrace customer in Europe. Thanks to the timely detection by Darktrace DETECT™ and the support of Darktrace’s Security Operations Center (SOC), the Pikabot compromise was quickly shut down before it could escalate into a more disruptive attack.

What is Pikabot?

Pikabot is one of the latest modular loader malware strains that has been active since the first half of 2023, with several evolutions in its methodology observed in the months since. Initial researchers noted similarities to the Qakbot aka Qbot or Pinkslipbot and Mantanbuchus malware families, and while Pikabot appears to be a new malware in early development, it shares multiple commonalities with Qakbot [1].

First, both Pikabot and Qakbot have similar distribution methods, can be used for multi-stage attacks, and are often accompanied by downloads of Cobalt Strike and other malware strains. The threat actor known as TA577, which has also been referred to as Water Curupira, has been seen to use both types of malware in spam campaigns which can lead to Black Basta ransomware attacks [2] [3].Notably, a rise in Pikabot campaigns were observed in September and October 2023, shortly after the takedown of Qakbot in Operation Duck Hunt, suggesting that Pikabot may be serving as a replacement for initial access to target network [4].

How does Pikabot malware work?

Many Pikabot infections start with a malicious email, particularly using email thread hijacking; however, other cases have been distributed via malspam and malvertising [5]. Once downloaded, Pikabot runs anti-analysis techniques and checks the system’s language, self-terminating if the language matches that of a Commonwealth of Independent States (CIS) country, such as Russian or Ukrainian. It will then gather key information to send to a command-and-control (C2) server, at which point additional payload downloads may be observed [2]. Early response to a Pikabot infection is important for organizations to prevent escalation to a significant compromise such as ransomware.

Darktrace’s Coverage of Pikabot malware

Between April and July 2023, the Darktrace Threat Research team investigated Pikabot infections affected more than 15 customer environments; these attacks primarily targeted US and European organizations spanning multiple industries, and most followed the below lifecycle:

  1. Initial access via malspam or email, often outside of Darktrace’s scope
  2. Suspicious executable download from a URI in the format /\/[a-z0-9A-Z]{3,}\/[a-z0-9A-Z]{5,}/ and using a Windows PowerShell user agent
  3. C2 connections to IP addresses on uncommon ports including 1194 and 2078
  4. Some cases involved further C2 activity to Cobalt Strike endpoints

In October 2023, a second campaign emerged that largely followed the same attack pattern, with a notable difference that cURL was used for the initial payload download as opposed to PowerShell. All the Pikabot cases that Darktrace has observed since October 2023 have used cURL, which could indicate a shift in approach from targeting Windows devices to multi-operating system environments.

Figure 1: Timeline of the Pikabot infection over a 2-hour period.

On October 17, 2023, Darktrace observed a Pikabot infection on the network of a European customer after an internal user seemingly clicked a malicious link in a phishing email, thereby compromising their device. As the customer did not have Darktrace/Email™ deployed on their network, Darktrace did not have visibility over the email. Despite this, DETECT was still able to provide full visibility over the network-based activity that ensued.

Darktrace observed the device using a cURL user agent when initiating the download of an unusual executable (.exe) file from an IP address that had never previously been observed on the network. Darktrace further recognized that the executable file was attempting to masquerade as a different file type, likely to evade the detection of security teams and their security tools. Within one minute, the device began to communicate with additional unusual IP addresses on uncommon ports (185.106.94[.]174:5000 and 80.85.140[.]152:5938), both of which have been noted by open-source intelligence (OSINT) vendors as Pikabot C2 servers [6] [7].

Figure 2: Darktrace model breach Event Log showing the initial file download, immediately followed by a connection attempt to a Pikabot C2 server.

Around 40 minutes after the initial download, Darktrace detected the device performing suspicious DNS tunneling using a pattern that resembled the Cobalt Strike Beacon. This was accompanied by beaconing activity to a rare domain, ‘wordstt182[.]com’, which was registered only 4 days prior to this activity [8]. Darktrace observed additional DNS connections to the endpoint, ‘building4business[.]net’, which had been linked to Black Basta ransomware [2].

Figure 3: The affected device making successful TXT DNS requests to known Black Basta endpoints.

As this customer had integrated Darktrace with the Microsoft Defender, Defender was able to contextualize the DETECT model breaches with endpoint insights, such as known threats and malware, providing customers with unparalleled visibility of the host-level detections surrounding network-level anomalies.

In this case, the behavior of the affected device triggered multiple Microsoft Defender alerts, including one alert which linked the activity to the threat actor Storm-0464, another name for TA577 and Water Curupira. These insights were presented to the customer in the form of a Security Integration alert, allowing them to build a full picture of the ongoing incident.

Figure 4: Security Integration alert from Microsoft Defender in Darktrace, linking the observed activity to the threat group Storm-0464.

As the customer had subscribed to Darktrace’s Proactive Threat Notification (PTN) service, the customer received timely alerts from Darktrace’s SOC notifying them of the suspicious activity associated with Pikabot. This allowed the customer’s security team to quickly identify the affected device and remove it from their environment for remediation.

Although the customer did have Darktrace RESPOND™ enabled on their network, it was configured in human confirmation mode, requiring manual application for any RESPOND actions. RESPOND had suggested numerous actions to interrupt and contain the attack, including blocking connections to the observed Pikabot C2 addresses, which were manually actioned by the customer’s security team after the fact. Had RESPOND been enabled in autonomous response mode during the attack, it would have autonomously blocked these C2 connections and prevented the download of any suspicious files, effectively halting the escalation of the attack.

Nonetheless, Darktrace DETECT’s prompt identification and alerting of this incident played a crucial role in enabling the customer to mitigate the threat of Pikabot, preventing it from progressing into a disruptive ransomware attack.

Figure 5: Darktrace RESPOND actions recommended from the initial file download and throughout the C2 traffic, ranging from blocking specific connections to IP addresses and ports to enforcing a normal pattern of life for the source device.

Conclusion

Pikabot is just one recent example of a modular strain of loader known for its adaptability and speed, seamlessly changing tactics from one campaign to the next and utilizing new infrastructure to initiate multi-stage attacks. Leveraging commonly used tools and services like Windows PowerShell and cURL, alongside anti-analysis techniques, this malware can evade the detection and often bypass traditional security tools.

In this incident, Darktrace detected a Pikabot infection in its early stages, identifying an anomalous file download using a cURL user agent, a new tactic for this particular strain of malware. This timely detection, coupled with the support of Darktrace’s SOC, empowered the customer to quickly identify the compromised device and act against it, thwarting threat actors attempting to connect to malicious Cobalt Strike and Black Basta servers. By preventing the escalation of the attack, including potential ransomware deployment, the customer’s environment remained safeguarded.

Had Darktrace RESPOND been enabled in autonomous response mode at the time of this attack, it would have been able to further support the customer by applying targeted mitigative actions to contain the threat of Pikabot at its onset, bolstering their defenses even more effectively.

Credit to Brianna Leddy, Director of Analysis, Signe Zaharka, Senior Cyber Security Analyst

Appendix

Darktrace DETECT Models

Anomalous Connection / Anomalous SSL without SNI to New External

Anomalous Connection / Application Protocol on Uncommon Port

Anomalous Connection / Multiple Connections to New External TCP Port

Anomalous Connection / New User Agent to IP Without Hostname

Anomalous Connection / Powershell to Rare External

Anomalous Connection / Rare External SSL Self-Signed

Anomalous Connection / Repeated Rare External SSL Self-Signed

Anomalous File / EXE from Rare External Location

Anomalous File / Masqueraded File Transfer

Anomalous File / Multiple EXE from Rare External Locations

Compromise / Agent Beacon to New Endpoint

Compromise / Beacon to Young Endpoint

Compromise / Beaconing Activity To External Rare

Compromise / DNS / DNS Tunnel with TXT Records

Compromise / New or Repeated to Unusual SSL Port

Compromise / SSL Beaconing to Rare Destination

Compromise / Suspicious Beaconing Behaviour

Compromise / Suspicious File and C2

Device / Initial Breach Chain Compromise

Device / Large Number of Model Breaches

Device / New PowerShell User Agent

Device / New User Agent

Device / New User Agent and New IP

Device / Suspicious Domain

Security Integration / C2 Activity and Integration Detection

Security Integration / Egress and Integration Detection

Security Integration / High Severity Integration Detection

Security Integration / High Severity Integration Incident

Security Integration / Low Severity Integration Detection

Security Integration / Low Severity Integration Incident

Antigena / Network / External Threat / Antigena File then New Outbound Block

Antigena / Network / External Threat / Antigena Suspicious Activity Block

Antigena / Network / External Threat / Antigena Suspicious File Block

Antigena / Network / Significant Anomaly / Antigena Breaches Over Time Block

Antigena / Network / Significant Anomaly / Antigena Controlled and Model Breach

Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Client Block

Antigena / Network / Significant Anomaly / Antigena Significant Anomaly from Client Block

Antigena / Network / Significant Anomaly / Antigena Significant Security Integration and Network Activity Block

List of Indicators of Compromise (IoC)

IOC - TYPE - DESCRIPTION + CONFIDENCE

128.140.102[.]132 - IP Address - Pikabot Download

185.106.94[.]174:5000 - IP Address: Port - Pikabot C2 Endpoint

80.85.140[.]152:5938 - IP Address: Port - Pikabot C2 Endpoint

building4business[.]net - Hostname - Cobalt Strike DNS Beacon

wordstt182[.]com - Hostname - Cobalt Strike Server

167.88.166[.]109 - IP Address - Cobalt Strike Server

192.9.135[.]73 - IP - Pikabot C2 Endpoint

192.121.17[.]68 - IP - Pikabot C2 Endpoint

185.87.148[.]132 - IP - Pikabot C2 Endpoint

129.153.22[.]231 - IP - Pikabot C2 Endpoint

129.153.135[.]83 - IP - Pikabot C2 Endpoint

154.80.229[.]76 - IP - Pikabot C2 Endpoint

192.121.17[.]14 - IP - Pikabot C2 Endpoint

162.252.172[.]253 - IP - Pikabot C2 Endpoint

103.124.105[.]147 - IP - Likely Pikabot Download

178.18.246[.]136 - IP - Pikabot C2 Endpoint

86.38.225[.]106 - IP - Pikabot C2 Endpoint

198.44.187[.]12 - IP - Pikabot C2 Endpoint

154.12.233[.]66 - IP - Pikabot C2 Endpoint

MITRE ATT&CK Mapping

TACTIC - TECHNIQUE

Defense Evasion - Masquerading: Masquerade File Type (T1036.008)

Command and Control - Application Layer Protocol: Web Protocols (T1071.001)

Command and Control - Non-Standard Port (T1571)

Command and Control - Application Layer Protocol: DNS (T1071.004)

Command and Control - Protocol Tunneling (T1572)

References

[1] https://news.sophos.com/en-us/2023/06/12/deep-dive-into-the-pikabot-cyber-threat/?&web_view=true  

[2] https://www.trendmicro.com/en_be/research/24/a/a-look-into-pikabot-spam-wave-campaign.html

[3] https://thehackernews.com/2024/01/alert-water-curupira-hackers-actively.html

[4] https://www.darkreading.com/cyberattacks-data-breaches/pikabot-malware-qakbot-replacement-black-basta-attacks

[5] https://www.redpacketsecurity.com/pikabot-distributed-via-malicious-ads-6/

[6] https://www.virustotal.com/gui/ip-address/185.106.94.174/detection

[7] https://www.virustotal.com/gui/ip-address/80.85.140.152/detection

[8] https://www.domainiq.com/domain?wordstt182.com

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
Brianna Luong (Leddy)
Sr. Technical Alliances Manager

More in this series

No items found.

Blog

/

Network

/

July 27, 2026

Hiding in Plain Sight: Uncovering a Multi-Stage Ransomware Attack Through Behavioral Detection

ransomware attackDefault blog imageDefault blog image

Why ransomware has changed

Ransomware attacks have continued to increase globally, with 698 incidents reported in May 2026, representing a 48% rise compared to 472 incidents in May 2025 [1]. At the same time, the ransomware landscape is evolving. Several major ransomware groups, including LockBit [2], have been disrupted by successful joint law enforcement operations, resulting in a shift away from a small number of dominant actors towards a more fragmented and distributed ecosystem. This is increasingly composed of smaller groups who play a specialized role in the attack, such as initial access brokers, affiliates or developers.

As a result, ransomware tactics, techniques, and procedures (TTPs) are becoming more diverse and less predictable. On top of this, adversaries are leveraging native tools and legitimate penetration testing frameworks to evade detection. Anomaly-based detection is therefore critical to identify pre-ransomware activity, rather than relying on signatures associated with a handful of well-known ransomware groups.

As these attacks often unfold over several days, there is a critical window for defenders to act. In this context, behavioral-based detection plays a vital role in identifying suspicious pre-ransomware activity, and enabling early intervention before encryption or exfiltration occurs.

Inside a modern ransomware intrusion

In early 2026, Darktrace detected activity within a customer’s environment related to a multi-stage ransomware intrusion from the initial compromise. This activity does not appear to be attributable to a specific ransomware group, and no known ransomware payload was observed until the final stage.

The attack aligns with a broader industry trend in which compromised virtual private network (VPN) credentials are used as an entry point, followed by rapid internal reconnaissance and lateral movement using legitimate administrative tools. This growing preference for native tools and legitimate frameworks in cyber-attacks illustrates that it is increasingly unreliable to depend solely on traditional indicators of compromise such as known malware signatures or exploit detection.

The intrusion also involved the use of Sliver, an open-source adversary emulation framework, which is increasingly observed in real-world attacks. Originally designed for penetration testing and red teaming, Sliver has gained traction among threat actors as a stealthier alternative to more heavily signatured frameworks such as Cobalt Strike. As a legitimate framework, its use further complicates detection for security tools that rely on known malicious signatures.

Darktrace’s detection of a ransomware event in a customer’s environment

The initial compromise appears to have occurred via compromised credentials used over the VPN shortly before, or at the onset of the first indicators of suspicious activity. While it remains unclear as to how or when the threat actors gained access to these credentials, the use of initial access brokers (IABs) is a common feature of modern ransomware operations. This suggests that access to the environment may have been established several days or weeks beforehand.

The intrusion unfolded over three days, presenting multiple opportunities for early detection and intervention before ransomware deployment. The attack progressed through a compressed but structured sequence: initial access and reconnaissance were completed within hours, followed by privilege escalation and lateral movement the next day, and culminating in data exfiltration and encryption shortly thereafter. Throughout each stage, distinct behavioral anomalies emerged across the network providing clear indicators of malicious activity well before the ransomware was deployed.

While Darktrace’s Autonomous Response capability was enabled within the customer’s environment, it was not fully configured across the impacted devices, allowing the attack to progress to ransomware deployment. Had Autonomous Response been fully deployed across the affected systems, it could have taken targeted action against the earliest stages of malicious activity, potentially disrupting the intrusion before it escalated.

Figure 1: Timeline of the attack progression.

Day 1: Reconnaissance and privilege escalation

The threat actor gained access via compromised VPN credentials and initiated internal reconnaissance. Darktrace detected anomalous scanning behavior, including unusual port scanning activity and widespread network enumeration.

Specifically, Darktrace detected a high volume of east-west scanning activity across a broad range of ports, with TCP connections targeting ports 21, 80, 445, 4899 and 8080. Associated URIs suggested the use of Nmap, a widely used penetration testing tool. This highlights how attackers often leverage legitimate penetration testing tools for malicious reconnaissance, enabling them to blend into normal network activity and evade traditional signature-based detection methods.

Figure 2: Darktrace's detection of a sharp increase in anomalous internal connections, triggering multiple high-severity model alerts associated with reconnaissance activity.

Several devices were observed using administrative credentials to carry out privileged actions in a manner that was highly anomalous for the environment. This activity was accompanied by behavior consistent with SMB authentication scanning, suggesting efforts to identify and access additional systems. As the activity intensified, an increasing number of devices became involved, signalling lateral movement and further spread across the network.

Darktrace also identified privilege escalation through active directory (AD) replication abuse, specifically via the drsuapi::DRSGetNCChanges function. This technique allows an attacker with sufficient privileges to request directory replication data from a domain controller (DC), enabling them to extract credentials, including password hashes, without directly interacting with user accounts. Commonly associated with ‘DCSync’ attacks, this technique is frequently used to obtain highly privileged credentials and enable further escalation within an environment.

Figure 3: Darktrace’s detection of anomalous AD replication activity indicative of privilege escalation.

This activity was seen alongside the use of the now obsolete SMBv1, repeated NTLM authentication attempts using multiple variations of ‘Administrator’ credentials, reverse DNS scanning, and large-scale network scanning. Darktrace observed widespread use of SMBv1 across the customer’s environment, exposing a significant security weakness. As a legacy protocol with well-documented weaknesses, SMBv1 can be exploited to facilitate lateral movement, allowing the attackers to expand their access following initial compromise.

Day 3: Lateral Movement, Command & Control, and Exfiltration

Two days later, the attacker escalated privileges and expanded their foothold using living-off-the-land (LOTL) techniques such as PSExec, WMI, and RDP. Concurrently, Darktrace identified command-and-control (C2)-style communications consistent with the Sliver framework, alongside rare outbound connections to cloud infrastructure indicating potential data exfiltration. The volume and severity of observed activity increased as attack behavior intensified.

The device was observed conducting extensive lateral movement, leveraging LOTL techniques to evade detection. Activity included WMI execution (e.g. ExecQuery), DCE-RPC activity, SMB sessions and file writes, most of which were successful, as well as the deployment of PSEXESVC.exe via ADMIN$ shares and prolonged RDP sessions. Darktrace identified this behavior as highly anomalous for the environment. Such activity is commonly associated with the transfer of attacker tooling, remote command execution, and the establishment of persistent access across compromised systems.  

Figure 4: Darktrace’s detection of a spike in RPC binding events indicative of potential lateral movement.

On the same day, Darktrace detected C2-style SSL communications originating from multiple internal devices to rare external endpoints. These connections exhibited anomalous characteristics, including invalid SSL certificates and repeated connection patterns resembling beaconing. Analysis of the observed JA3 fingerprint further linked the activity to Sliver, the adversary simulation framework referenced earlier, as the hash has previously been associated with Sliver-related infrastructure [3]. The use of this framework reflects a broader trend of attackers repurposing legitimate offensive security tools for stealthy C2 communications. Connections to 137[.]220[.]59[.]55 (ASN AS20473 AS-VULTR) indicated that the communications were likely routed via a virtual private server (VPS) hosted by Vultr. Attackers often utilize VPS infrastructure from legitimate cloud providers like Vultr to obscure their true origin, blend into benign traffic, and evade IP-based detection mechanisms [4].

Figure 5: Darktrace’s Cyber AI Analyst detection of two linked unusual connections to Vultr infrastructure.

Darktrace also observed a device initiating SSL connections to safedata.s3[.]wasabisys[.]com, an endpoint associated with Wasabi cloud storage. Darktrace recognized that neither the destination nor the associated IP address had previously been observed within the environment.  More than 200 MB of data was subsequently uploaded externally to endpoints sharing the same JA3 client hash, indicating a sustained transfer session and potential data exfiltration to third-party storage. The apparent exfiltration prior to encryption is consistent with a double-extortion ransomware strategy.

Figure 6: Darktrace’s Cyber AI Analyst detection of more than 30 rare outbound connections to a Wasabi cloud storage endpoint, indicative of potential data exfiltration

Day 4: Encryption

The attack culminated in ransomware deployment, marking the transition from suspicious network activity to a business-impacting incident. Using SMB-based propagation, the threat actor encrypted thousands of files across the network, affecting multiple systems and disrupting normal operations. Throughout the encryption event, the legacy SMBv1 protocol was used extensively across multiple internal systems, resulting in a significant increase in newly encrypted files.

Figure 7: Darktrace’s detection of abnormal spikes in SMB activity and associated model alerts, indicative of ransomware encryption and propagation.

Darktrace’s Cyber AI Analyst automatically investigated and correlated the encryption activity and related events into a single incident narrative, providing the customer with real-time visibility into the attack while significantly reducing investigation time.

Figure 8: Darktrace’s Cyber AI Analyst’s investigation into the encryption activity. AI Analyst incident detailing example encryption activity in real time. Related events are automatically correlated and summarized into a clear narrative, reducing investigation time.

Defender action recommendations

What Could Have Stopped the Attack Earlier?

Although the attack ultimately resulted in ransomware deployment, there were multiple opportunities to detect, contain, and disrupt the intrusion before encryption occurred. The following actions could have significantly reduced the overall impact:

Detect and investigate indicators of reconnaissance and lateral movement

  • Unusual scanning
  • Active Directory replication anomalies consistent with DCSync activity
  • Anomalous use of native tools and processes indicative of LOTL attacks
  • Unusual use of common reconnaissance tools such as Nmap and NetScan

Contain compromised credentials and affected devices

  • Disable and reset compromised VPN credentials
  • Isolate devices performing anomalous scanning and lateral movement activity

Block suspicious external communications and data exfiltration

  • Use anomaly-based detection to detect and block repeated outbound connections to rare external infrastructure
  • Prevent data exfiltration to unauthorized cloud storage services such as Wasabi

Conclusion

The incident highlights the importance of anomaly-based detection, particularly against attacks that primarily use native or legitimate tools to evade traditional security measures. Darktrace identified suspicious activity from the first day of the compromise, providing multiple opportunities to disrupt the intrusion before it progressed to lateral movement and data exfiltration.

In this instance, detection was not the limiting factor; response time was. Prompt investigation and containment of devices exhibiting anomalous behavior could have prevented lateral movement, data exfiltration, and ultimately ransomware deployment.

As adversaries increasingly prioritize stealth over custom malware, relying instead on legitimate tools, valid credentials, and trusted infrastructure, traditional signature-based detection becomes less effective. Identifying subtle behavioral deviations early remains critical to disrupting attacks before they escalate into full-scale ransomware incidents.

Credit to Alexandra Evzona (Cyber Analyst), Priya Thapa (Senior Cyber Analyst)
Edited by Ryan Traill (Content Manager)

Appendices

References

[1] https://industrialcyber.co/ransomware/check-point-reports-ransomware-attacks-jump-48-year-over-year-despite-decline-in-overall-cyberattack-activity/

[2] https://www.europol.europa.eu/media-press/newsroom/news/law-enforcement-disrupt-worlds-biggest-ransomware-operation

[3] https://fieldeffect.com/blog/field-effect-mitigates-not-so-simplehelp-exploits-enabling-deployment-of-backdoors

[4] https://www.darktrace.com/blog/from-vps-to-phishing-how-darktrace-uncovered-saas-hijacks-through-virtual-infrastructure-abuse

Indicators of Compromise (IoCs)

IP Addresses

  • 137[.]220[.]59[.]55 – Potential C2 infrastructure (Vultr AS20473)
  • 38[.]27[.]106[.]123 – Wasabi cloud storage endpoint associated with potential data exfiltration
  • 38[.]27[.]106[.]128 – Wasabi cloud storage endpoint associated with potential data exfiltration
  • 38[.]27[.]106[.]117 – Wasabi cloud storage endpoint associated with potential data exfiltration

Domains

  • safedata[.]s3[.]wasabisys[.]com – Potential data exfiltration endpoint
  • *.wasabisys[.]com – Associated Wasabi cloud storage infrastructure

JA3 Fingerprint

  • d6828e30ab66774a91a96ae93be4ae4c – Associated with the Sliver adversary emulation framework

Files

  • Delete[.]me – File observed during reconnaissance activity, commonly associated with NetScan

Darktrace Model Coverage

·       Anomalous Connection / Active Remote Desktop Tunnel

·       Anomalous Connection / Anomalous Remote Registry Service Control

·       Anomalous Connection / Multiple Failed Windows UDP

·       Anomalous Connection / New or Uncommon Service Control

·       Anomalous Connection / New or Uncommon Service Enumeration

·       Anomalous Connection / New User Agent to IP Without Hostname

·       Anomalous Connection / SMB Enumeration

·       Anomalous Connection / Suspicious Activity On High Risk Device

·       Anomalous Connection / Suspicious Read Write Ratio

·       Anomalous Connection / Sustained MIME Type Conversion

·       Anomalous Connection / Uncommon 1 GiB Outbound

·       Anomalous Connection / Unusual Admin RDP Session

·       Anomalous Connection / Unusual Admin SMB Session

·       Anomalous Connection / Unusual SMB Version 1 Connectivity

·       Anomalous File / EXE from Rare External Location

·       Anomalous File / Internal / Additional Extension Appended to SMB File

·       Anomalous Server Activity / Outgoing from Server

·       Compromise / Beaconing Activity To External Rare

·       Compromise / Ransomware / Possible Ransom Note Read

·       Compromise / Ransomware / Ransom or Offensive Words Written to SMB

·       Compromise / Ransomware / Suspicious SMB Activity

·       Device / Anonymous NTLM Logins

·       Device / Attack and Recon Tools

·       Device / Initial Attack Chain Activity

·       Device / Large Number of Model Alerts

·       Device / Long Agent Connection to New Endpoint

·       Device / Multiple Lateral Movement Model Alerts

·       Device / Network Scan

·       Device / New or Uncommon SMB Named Pipe

·       Device / New or Unusual Remote Command Execution

·       Device / New User Agent

·       Device / Possible RPC Lateral Movement

·       Device / Possible SMB/NTLM Brute Force

·       Device / RDP Scan

·       Device / SMB Lateral Movement

·       Device / SMB Session Brute Force (Non-Admin)

·       Device / SMB Version 1 Access Failures

·       Device / Suspicious File Delete Activity

·       Device / Suspicious Network Scan Activity

·       Device / Unusual SMB Error Detected

·       Device / Unusual SMB To Critical Resource

·       Device / Unusual Winreg Operation

·       Unusual Activity / Multiple Failed Internal Connections

·       Unusual Activity / Possible RPC Recon Activity

·       Unusual Activity / Sustained Anomalous SMB Activity

·       Unusual Activity / Unusual External Data to New Endpoint

·       Unusual Activity / Unusual External Data Transfer

·       Unusual Activity / Unusual File Storage Data Transfer

·       Unusual Activity / Unusual Large Internal Transfer

·       User / New Admin Credentials on Client

·       User / NTLM Login from Unauthenticated Device

Autonomous Response Model Alerts

·       Antigena / Network / External Threat / Antigena Ransomware Block

·       Antigena / Network / External Threat / Antigena Suspicious File Block

·       Antigena / Network / Insider Threat / Antigena Active Threat SMB Write Block

·       Antigena / Network / Insider Threat / Antigena Internal Anomalous File Activity

·       Antigena / Network / Insider Threat / Antigena Large Data Volume Outbound Block

·       Antigena / Network / Insider Threat / Antigena Network Scan Block

·       Antigena / Network / Insider Threat / Antigena Unusual Privileged User Activities Block

·       Antigena / Network / Manual / Quarantine Device

·       Antigena / Network / Significant Anomaly / Antigena Alerts Over Time Block

·       Antigena / Network / Significant Anomaly / Antigena Controlled and Model Alert

·       Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Client Block

·       Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Server Block 100

·       Antigena / Network / Significant Anomaly / Antigena Significant Anomaly from Client Block

MITRE ATT&CK MAPPING

Command and control - Protocol Tunneling - T1572

Command and control – Web Protocols – T1071.001

Credential Access- Exploitation for Credential Access- T1212

Credential Access- Password Guessing- T1110

Discovery- File and Directory Discovery- T1083

Discovery- Network Service Discovery- T1046

Discovery- Network Share Discovery- T1135

Discovery- Remote System Discovery- T1018

Exfiltration- Exfiltration Over C2 Channel- T1041

Exfiltration- Exfiltration to Cloud Storage- T1567

Impact- Data Encrypted for Impact- T1486

Impact- Data Encrypted for Impact- T1486

Impact- Service Stop - T1489

Initial Access- Public-Facing Application- T1190

Lateral Movement- Exploitation of Remote Services- T1210

Lateral Movement- Remote Desktop Protocol- T1021

Lateral Movement- SMB/Windows Admin Shares- T1021

Lateral Movement- Taint Shared Content- T1080

Persistence- Modify Registry- T1112

Privilege Escalation- Exploitation for Privilege Escalation- T0890

Privilege Escalation- Valid Accounts- T1078

Reconnaissance- Scanning IP Blocks- T1595

Reconnaissance- Vulnerability Scanning- T1595

Resource Development- Malware- T1588

Stealth- File Deletion- T1070

Continue reading
About the author
Alexandra Evzona
Cyber Analyst

Blog

/

Email

/

July 24, 2026

Darktrace / EMAIL Expands Behavioral Defense Across Email and Collaboration Workflows

Default blog imageDefault blog image

Email and collaboration tools do more than carry messages. They are where organizations approve payments, share sensitive data, reset credentials, and make thousands of everyday decisions. Increasingly, they are interfaces through which humans direct AI agents in their daily activity. Email, Slack and Teams are high volume, rich with sensitive data, and an easy place to hide malicious activity.

The opportunity isn’t lost on bad actors. Darktrace / EMAIL detected more than 32 million high-confidence phishing emails globally in 2025, and 70% of those messages passed DMARC authentication.  Phishing is increasingly difficult to detect and familiar trust signals alone are not enough. People and security teams need to understand how a message fits the normal behavior of the sender, recipient, and organization. They also need to correlate activity across platforms to spot threats that span multiple channels.

To effectively secure against today’s evolved threats, security teams need to act at two levels: they need to help each employee make a safer decision ‘in the moment’, and they need to understand the wider patterns that may expose the business to risk.

Darktrace is introducing four new capabilities in Darktrace / EMAIL to address both challenges. The new features explain suspicious content more clearly to end users, strengthen the capabilities of Darktrace / Adaptive Human Defense with richer guidance, let organizations define their own patterns for detecting sensitive data in messages, and give security teams a process-level view of risk across email and collaboration workflows.

Darktrace / EMAIL Inbox Analysis highlights risky content within your emails

A warning is more useful when it explains what the user should look at. To help do that, we’ve expanded Darktrace / EMAIL’s Inbox Analysis Add-In to highlight potentially dangerous content within the body of emails that Darktrace / EMAIL flags as potentially suspicious or high risk.  

The add-in can highlight language designed to create urgency, financial references, requests for payment, suspicious links, and content that is unusual for the sender. Each highlighted element includes a pop up that explains why it may be suspicious. Instead of asking an employee to accept a verdict without context, the analysis helps them examine the message and make a more informed decision.

Enhanced Just-In-Time Training Banners in Darktrace / Adaptive Human Defense

Enhanced Just-In-Time Training Banners build on the same principle. The banners now include a contextual header, actionable advice, and specific detection context. This gives employees more useful guidance at the point of risk without adding unnecessary information or cognitive load.

Together, the capabilities help turn a warning into a short learning moment. Employees can see what looks unusual, understand what action to take, and build their judgment.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention

Sensitive data is different for every business. Standard categories such as payment card details or government identifiers matter, but organizations also have their own customer codes, project names, research formats, account structures, and internal identifiers.

Custom Sensitive Data Detection in Darktrace / EMAIL - Data Loss Prevention allows administrators to write custom expressions for the data their organization needs to protect. Matched content can trigger existing model actions and data loss prevention (DLP) workflows, extending Darktrace's DLP capabilities.

This extends data loss detection beyond a fixed library of common data types. Security teams can apply controls to information that is sensitive in the context of their own organization and adapt those controls as the business changes.

Introducing Email and Collaboration Workflow Risk Posture Dashboards

Some of the most important risks are not isolated events. They are repeated ways of working that create an opening for error, misuse, or attack. For example, a payment request may be one suspicious message, but a recurring approval workflow that relies on weak verification is a business process risk.

The new Email and Collaboration Workflow Risk Posture Dashboard analyzes email and collaboration data across Email, Microsoft Teams, Slack and Zoom to provide a process-level view of risk in the organization. These may include financial authorization workflows, sensitive data sharing patterns, and activity that could expose credentials.

The dashboard brings these patterns into a view and provides actionable recommendations. This helps security teams determine where to investigate or strengthen controls, where ownership needs to be clarified, and where the business may need to change a risky process. It gives CISOs a clearer view of how human and communication risk is embedded in everyday operations, not only where individual alerts occur.

Behavior connects the individual decision to the wider risk

These capabilities build on Darktrace’s unique behavioral approach to security. We use Adaptive AI to learn how people and AI normally behave within an organization, creating the context needed to recognize when activity changes.

Within the Darktrace Behavioral Defense Platform, Darktrace / EMAIL helps protect people against phishing, account takeover, data exfiltration, and human risk across email and collaboration tools. The new capabilities extend that protection in both directions. They give employees clearer context for the decision in front of them, while giving security leaders a broader view of the workflows and behavior that create risk across the organization.

The result is not simply more alerts. It is a better understanding of why something is risky, what action to take, and where the organization can reduce risk before a familiar process becomes an easy route for an attacker.

[related-resource]

Continue reading
About the author
Carlos Gray
Senior Product Marketing Manager, Email
Your data. Our AI.
Elevate your network security with Darktrace AI