Darktrace's autonomous response successfully thwarted a Trickbot intrusion. See how AI played a crucial role in this defense.
Widespread use of the cloud continues to transform business, while cyber security solutions race to keep up. Today’s multi-cloud environments introduce complexity and gaps in visibility that open doors for attackers. Given the dynamic nature of the cloud, these blind spots are constantly changing. And given its scalability, simple mistakes like a minor misconfiguration can lead to disproportionately large security incidents.
Enterprises can no longer afford to rely on disparate tools and static, point-in-time views of risk. The cloud is inherently complex, and security tools shouldn’t aim to simplify that complexity, but instead harness it, using its scale and intricacy to its advantage.
In a world where the cloud is highly customizable and every cloud is different, a one-size-fits-all approach to cloud security fails to adapt to the nuances of an individual environment. This blog explores how harnessing AI that learns and understands the unique organization can give security teams the visibility, understanding, and real-time detection and response needed to secure the cloud.
Security hinges on action
Typically, cloud security tends to fall into one of two camps:
Agentless approaches used by most Cloud Security Posture Management (CSPM) vendors that promise quick and easy installation with minimal disruption of operations, and
Agent-based approaches that offer finer granularity but may mean a lengthy, time-consuming, and expensive set-up process.
Both approaches have inherent drawbacks. Agentless solutions typically don’t give security teams the real-time awareness needed to detect emerging threats – be that a malicious insider, a zero-day exploit, or something else. On the other hand, agent-based solutions provide limited reach and scalability, usually being deployed in an area of the cloud the security team already knew posed a risk, offering no new insight and leaving blind spots untouched.
So cloud security today seems to be stuck in a dilemma. And another issue for both methods is that these products may be able to alert analysts when something goes wrong, but lack the ability to mount a genuine response. Even newer solutions claiming to provide automated response are usually referring to automating the process of sending alerts and opening tickets.
Rapid response is the holy grail
The same attributes that make the cloud so useful and attractive to organizations – speed, agility, availability, and scale – hold a symmetrical appeal for attackers. When cyber-attacks in the cloud unfold rapidly, it’s not enough to simply open a ticket and wait for somebody on the other end to pick it up. (If anything, having to field too many tickets can actually bog down triage and investigation, and delay rather than hasten response.) The ultimate test for useful response comes down to whether or not the security team is willing to use it. Response capabilities that never get turned on, with security teams fearful of disruption, miss the point entirely.
Effective response requires an understanding of when and how to respond, as well as having the cloud-native mechanisms to carry out the action. We can break this down into three steps:
Today’s static cloud security solutions provide snapshots of your environment prior to integration and installation. Static insights help validate and set up controls before deployment, but the real risks related to cloud migration appear later.
To drive the right response, your security solution must deliver a real-time, holistic view of your organization’s cloud environment, not just a generic sense of what the environment looks like.
Understanding risk related to the cloud requires more than just visibility. It requires understanding the various patterns of behavior across the environment, and knowing the nuances in how applications and workloads are architected. Who has access to what? Which virtual machines typically connect with each other? Is this container behaving as expected? Is this new Lambda function expected?
Darktrace / CLOUD uses Self-Learning AI to see and understand your unique organization at the cloud network, architectural, and management layers. The ability of AI to recognize patterns across vast quantities of data puts it in a unique position to give security teams genuine insight into what’s happening in their cloud environment right now.
Each deployment and specific use of AI is different (based on your unique environment) but always includes an architectural view of your cloud footprint that aligns security and DevOps teams throughout the deployment lifecycle.
One beta customer reported deploying Darktrace/Cloud was:
like flipping on a light switch in a dark room."
Step 2: Detection must apply context
With a true understanding of exactly what’s ‘normal’ in your cloud – which users are connecting to what resources, who has access to specific workloads, groups, overlaps, and privileges — the solution progresses toward response by teaching itself to spot what isn’t so normal.
A static snapshot of your cloud security posture can surface unpatched vulnerabilities and problematic misconfigurations, but the insight ends there. Cloud security solutions based on static views and point-in-time visibility can’t connect the dots to deliver the end-goal: the ability to spot real-time threats.
Darktrace/Cloud delivers meaningful insight into vulnerabilities and misconfigurations, but its real-time understanding also enables detection of emerging threats. And combining with other Darktrace modules like Darktrace / NETWORK and Darktrace/Email, it enriches these findings with business context to find and shut down emerging threats in seconds. This business-wide context to understand your cloud footprint and how it interacts with your on-premises infrastructure, endpoints, and applications
Step 3: Response must be truly autonomous
By understanding your unique cloud footprint within the context of your own business, Darktrace/Cloud uniquely detects when something unusual is occurring that requires a response right now.
The use of AI to understand your environment enables a truly autonomous and precise cloud-native response. The platform can take targeted action to stop only the threatening behaviors as they appear, without disrupting regular business operations.
Because the platform understands your complete cloud architecture, it also knows what cloud-native mechanisms are at its disposal to initiate a real response. Automated real-time responses include cloud-native actions like detaching EC2 instances and applying security groups to contain risky assets.
See it in action
Darktrace is offering 30-day free trials of Darktrace/Cloud that combine easy install with unprecedented understanding of multi-cloud environments. Click here to register your interest and experience the benefits first-hand.
Like this and want more?
Receive the latest blog in your inbox
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Newsletter
Enjoying the blog?
Sign up to receive the latest news and insights from the Darktrace newsletter – delivered directly to your inbox
Thanks for signing up!
Look out for your first newsletter, coming soon.
Oops! Something went wrong while submitting the form.
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.
Bytesize Security: Insider Threats in Google Workspace
What is an insider threat?
An insider threat is a cyber risk originating from within an organization. These threats can involve actions such as an employee inadvertently clicking on a malicious link (e.g., a phishing email) or an employee with malicious intent conducting data exfiltration for corporate sabotage.
Insiders often exploit their knowledge and access to legitimate corporate tools, presenting a continuous risk to organizations. Defenders must protect their digital estate against threats from both within and outside the organization.
For example, in the summer of 2024, Darktrace / IDENTITY successfully detected a user in a customer environment attempting to steal sensitive data from a trusted Google Workspace service. Despite the use of a legitimate and compliant corporate tool, Darktrace identified anomalies in the user’s behavior that indicated malicious intent.
Attack overview: Insider threat
In June 2024, Darktrace detected unusual activity involving the Software-as-a-Service (SaaS) account of a former employee from a customer organization. This individual, who had recently left the company, was observed downloading a significant amount of data in the form of a “.INDD” file (an Adobe InDesign document typically used to create page layouts [1]) from Google Drive.
While the use of Google Drive and other Google Workspace platforms was not unexpected for this employee, Darktrace identified that the user had logged in from an unfamiliar and suspicious IPv6 address before initiating the download. This anomaly triggered a model alert in Darktrace / IDENTITY, flagging the activity as potentially malicious.
Following this detection, the customer reached out to Darktrace’s Security Operations Center (SOC) team via the Security Operations Support service for assistance in triaging and investigating the incident further. Darktrace’s SOC team conducted an in-depth investigation, enabling the customer to identify the exact moment of the file download, as well as the contents of the stolen documents. The customer later confirmed that the downloaded files contained sensitive corporate data, including customer details and payment information, likely intended for reuse or sharing with a new employer.
In this particular instance, Darktrace’s Autonomous Response capability was not active, allowing the malicious insider to successfully exfiltrate the files. If Autonomous Response had been enabled, Darktrace would have immediately acted upon detecting the login from an unusual (in this case 100% rare) location by logging out and disabling the SaaS user. This would have provided the customer with the necessary time to review the activity and verify whether the user was authorized to access their SaaS environments.
Conclusion
Insider threats pose a significant challenge for traditional security tools as they involve internal users who are expected to access SaaS platforms. These insiders have preexisting knowledge of the environment, sensitive data, and how to make their activities appear normal, as seen in this case with the use of Google Workspace. This familiarity allows them to avoid having to use more easily detectable intrusion methods like phishing campaigns.
Darktrace’s anomaly detection capabilities, which focus on identifying unusual activity rather than relying on specific rules and signatures, enable it to effectively detect deviations from a user’s expected behavior. For instance, an unusual login from a new location, as in this example, can be flagged even if the subsequent malicious activity appears innocuous due to the use of a trusted application like Google Drive.
Credit to Vivek Rajan (Cyber Analyst) and Ryan Traill (Analyst Content Lead)
Appendices
Darktrace Model Detections
SaaS / Resource::Unusual Download Of Externally Shared Google Workspace File
RansomHub Ransomware: Darktrace’s Investigation of the Newest Tool in ShadowSyndicate's Arsenal
What is ShadowSyndicate?
ShadowSyndicate, also known as Infra Storm, is a threat actor reportedly active since July 2022, working with various ransomware groups and affiliates of ransomware programs, such as Quantum, Nokoyawa, and ALPHV. This threat actor employs tools like Cobalt Strike, Sliver, IcedID, and Matanbuchus malware in its attacks. ShadowSyndicate utilizes the same SSH fingerprint (1ca4cbac895fc3bd12417b77fc6ed31d) on many of their servers—85 as of September 2023. At least 52 of these servers have been linked to the Cobalt Strike command and control (C2) framework [1].
What is RansomHub?
First observed following the FBI's takedown of ALPHV/BlackCat in December 2023, RansomHub quickly gained notoriety as a Ransomware-as-a-Service (RaaS) operator. RansomHub capitalized on the law enforcement’s disruption of the LockBit group’s operations in February 2024 to market themselves to potential affiliates who had previously relied on LockBit’s encryptors. RansomHub's success can be largely attributed to their aggressive recruitment on underground forums, leading to the absorption of ex-ALPHV and ex-LockBit affiliates. They were one of the most active ransomware operators in 2024, with approximately 500 victims reported since February, according to their Dedicated Leak Site (DLS) [2].
ShadowSyndicate and RansomHub
External researchers have reported that ShadowSyndicate had as many as seven different ransomware families in their arsenal between July 2022, and September 2023. Now, ShadowSyndicate appears to have added RansomHub’s their formidable stockpile, becoming an affiliate of the RaaS provider [1].
Darktrace’s analysis of ShadowSyndicate across its customer base indicates that the group has been leveraging RansomHub ransomware in multiple attacks in September and October 2024. ShadowSyndicate likely shifted to using RansomHub due to the lucrative rates offered by this RaaS provider, with affiliates receiving up to 90% of the ransom—significantly higher than the general market rate of 70-80% [3].
In many instances where encryption was observed, ransom notes with the naming pattern “README_[a-zA-Z0-9]{6}.txt” were written to affected devices. The content of these ransom notes threatened to release stolen confidential data via RansomHub’s DLS unless a ransom was paid. During these attacks, data exfiltration activity to external endpoints using the SSH protocol was observed. The external endpoints to which the data was transferred were found to coincide with servers previously associated with ShadowSyndicate activity.
Darktrace’s coverage of ShadowSyndicate and RansomHub
Darktrace’s Threat Research team identified high-confidence indicators of compromise (IoCs) linked to the ShadowSyndicate group deploying RansomHub. The investigation revealed four separate incidents impacting Darktrace customers across various sectors, including education, manufacturing, and social services. In the investigated cases, multiple stages of the kill chain were observed, starting with initial internal reconnaissance and leading to eventual file encryption and data exfiltration.
Attack Overview
Internal Reconnaissance
The first observed stage of ShadowSyndicate attacks involved devices making multiple internal connection attempts to other internal devices over key ports, suggesting network scanning and enumeration activity. In this initial phase of the attack, the threat actor gathers critical details and information by scanning the network for open ports that might be potentially exploitable. In cases observed by Darktrace affected devices were typically seen attempting to connect to other internal locations over TCP ports including 22, 445 and 3389.
C2 Communication and Data Exfiltration
In most of the RansomHub cases investigated by Darktrace, unusual connections to endpoints associated with Splashtop, a remote desktop access software, were observed briefly before outbound SSH connections were identified.
Following this, Darktrace detected outbound SSH connections to the external IP address 46.161.27[.]151 using WinSCP, an open-source SSH client for Windows used for secure file transfer. The Cybersecurity and Infrastructure Security Agency (CISA) identified this IP address as malicious and associated it with ShadowSyndicate’s C2 infrastructure [4]. During connections to this IP, multiple gigabytes of data were exfiltrated from customer networks via SSH.
Data exfiltration attempts were consistent across investigated cases; however, the method of egress varied from one attack to another, as one would expect with a RaaS strain being employed by different affiliates. In addition to transfers to ShadowSyndicate’s infrastructure, threat actors were also observed transferring data to the cloud storage and file transfer service, MEGA, via HTTP connections using the ‘rclone’ user agent – a command-line program used to manage files on cloud storage. In another case, data exfiltration activity occurred over port 443, utilizing SSL connections.
Lateral Movement
In investigated incidents, lateral movement activity began shortly after C2 communications were established. In one case, Darktrace identified the unusual use of a new administrative credential which was quickly followed up with multiple suspicious executable file writes to other internal devices on the network.
The filenames for this executable followed the regex naming convention “[a-zA-Z]{6}.exe”, with two observed examples being “bWqQUx.exe” and “sdtMfs.exe”.
Additionally, script files such as “Defeat-Defender2.bat”, “Share.bat”, and “def.bat” were also seen written over SMB, suggesting that threat actors were trying to evade network defenses and detection by antivirus software like Microsoft Defender.
File Encryption
Among the three cases where file encryption activity was observed, file names were changed by adding an extension following the regex format “.[a-zA-Z0-9]{6}”. Ransom notes with a similar naming convention, “README_[a-zA-Z0-9]{6}.txt”, were written to each share. While the content of the ransom notes differed slightly in each case, most contained similar text. Clear indicators in the body of the ransom notes pointed to the use of RansomHub ransomware in these attacks. As is increasingly the case, threat actors employed double extortion tactics, threatening to leak confidential data if the ransom was not paid. Like most ransomware, RansomHub included TOR site links for communication between its "customer service team" and the target.
Since Darktrace’s Autonomous Response capability was not enabled during the compromise, the ransomware attack succeeded in its objective. However, Darktrace’s Cyber AI Analyst provided comprehensive coverage of the kill chain, enabling the customer to quickly identify affected devices and initiate remediation.
In lieu of Autonomous Response being active on the networks, Darktrace was able to suggest a variety of manual response actions intended to contain the compromise and prevent further malicious activity. Had Autonomous Response been enabled at the time of the attack, these actions would have been quickly applied without any human interaction, potentially halting the ransomware attack earlier in the kill chain.
Conclusion
The Darktrace Threat Research team has noted a surge in attacks by the ShadowSyndicate group using RansomHub’s RaaS of late. RaaS has become increasingly popular across the threat landscape due to its ease of access to malware and script execution. As more individual threat actors adopt RaaS, security teams are struggling to defend against the increasing number of opportunistic attacks.
For customers subscribed to Darktrace’s Security Operations Center (SOC) services, the Analyst team promptly investigated detections of the aforementioned unusual and anomalous activities in the initial infection phases. Multiple alerts were raised via Darktrace’s Managed Threat Detection to warn customers of active ransomware incidents. By emphasizing anomaly-based detection and response, Darktrace can effectively identify devices affected by ransomware and take action against emerging activity, minimizing disruption and impact on customer networks.
Credit to Kwa Qing Hong (Senior Cyber Analyst and Deputy Analyst Team Lead, Singapore) and Signe Zahark (Principal Cyber Analyst, Japan)