Blog
/
/
November 29, 2020

Darktrace Cyber Analyst Investigates Sodinokibi Ransomware

Darktrace’s Cyber AI Analyst uncovers the intricate details of a Sodinokibi ransomware attack on a retail organization. Dive into this real-time incident.
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
Max Heinemeyer
Global Field CISO
Default blog image
29
Nov 2020

Sodinokibi is one of the most lucrative ransomware strains of 2020, with its creators, cyber-criminal gang REvil, recently claiming over $100 million in profits this year alone. The prevalent threat is known to wipe backup files, encrypt files on local shares and exfiltrate data.

Exfiltration before encryption is a technique being increasingly adopted by profit-seeking cyber-criminals, who can threaten to leak the stolen data should a target organization not comply with their demands. Sodinobiki also makes heavy use of code obfuscation and encryption techniques to evade detection by signature-based, anti-virus solutions.

Darktrace’s AI recently detected Sodinokibi targeting a retail organization in the US. Prior to this year, the company operated primarily face-to-face in physical stores, but have conducted the majority of their business in the digital realm since the onset of the pandemic.

Cyber AI Analyst automatically launched a full investigation into this incident in real time, as the attack was unfolding. The technology provided summary reports of the entire incident which the security team could immediately action for incident response. This blog explores its findings.

Sodinokibi timeline

Darktrace automatically investigated on the full scope of the Sodinokibi attack, with Cyber AI Analyst clearly identifying and summarising every stage of the attack lifecycle, which played out over the course of three weeks as below:

Figure 1: A timeline of the attack

Darktrace produced a large number of security-relevant anomalies associated with just three credentials, and displayed these along a common timeline shown below:

Figure 2: A timeline view of anomaly detections separated by users. Note the clusters of model breaches for the compromised credentials leading up to October 14.

While a human analyst might have been able to identify these unusual patterns and investigate what caused the clusters of anomalous activity, this process would have taken precious hours during a crisis. Cyber AI Analyst automatically performed the same analysis using supervised machine learning trained on Darktrace’s world-leading analysts, generating meaningful summaries of each stage of the event in real time, as the incident unfolded.

REvil ransomware attack

The following events occurred during a free trial period, and Darktrace was not being actively monitored. Its Autonomous Response technology, Darktrace Antigena, was installed in passive mode, and in the absence of automatic interference at an early stage, this compromise was allowed to unfold without interruption. However, with Darktrace’s AI learning normal ‘patterns of life’ for every device in the background, identifying anomalies, and launching an automated investigation into the attack, we are able to go back into the Threat Visualizer and see how the incident unfolded.

The attack began when the credentials of a highly privileged member of the retail organization’s IT team were compromised. REvil is known to make use of phishing emails, exploit kits, server vulnerabilities, and compromised MSP networks for initial intrusion.

In this case, the attacker used the IT credential to compromise a domain controller and exfiltrate data directly after initial reconnaissance. Darktrace’s AI detected the attacker logging into the domain controller via SMB, writing suspicious files and then deleting batch scripts and log files in the root directory to clear their tracks.

The domain controller then made connections to several rare external endpoints, and Darktrace witnessed a 28MB upload that was likely exfiltration of initial reconnaissance data. Four days later, the attacker connected to the same endpoint (sadstat[.]com) – likely a stager download for C2, which was then initiated via connections on port 443 later that same day.

A week on from the intial C2 connection, a SQL server was detected engaging in network scanning as the attacker sought to move laterally in search of sensitive and valuable data. Over the course of two weeks, Darktrace witnessed unusual internal RDP connections using administrative credentials, before data was uploaded to multiple cloud storage endpoints as well as an SSH server. PsExec was used to deploy the ransomware, resulting in file encryption.

The evasive nature of modern ransomware

REvil started with an inherent advantage in that they were armed with the credentials of a highly privileged IT admin. Nevertheless, they still made several attempts to evade traditional, signature-based tools, such as ‘Living off the Land’ – using common tools such PsExec, WMI, RDP to blend into to legitimate activity.

They leveraged frequently-used cloud storage solutions like Dropbox and pCloud for data transfer, and they conducted SSH on port 443, blending in with SSL connections on the same port. They used a newly-registered domain for C2 communication, meaning Open Source Intelligence Tools (OSINT) were blind to the threat.

Finally, the malware itself was evasive in that it made use of code obfuscation and encryption, and had no need for a system library or API imports. This is the basis for most modern ransomware attacks, and the reality is signature-based tools cannot keep up. Darktrace’s AI not only detected the anomalous activity associated with every stage of the attack, but generated fleshed-out summaries of each stage of the attack with Cyber AI Analyst.

Cyber AI Analyst: Real-time incident reporting

Between September 21 and October 12, Cyber AI Analyst created 15 incidents, investigating dozens of point detections and creating a coherent attack narrative.

Figure 3: Cyber AI Incident log of the first compromised DC. This incident tab details the connections to sadstat[.]com

Figure 4: The DC establishes C2 to the first GHOSTnet GmbH IP

Figure 5: This incident tab highlights the file encryption of files on network shares

Figure 6: Darktrace surfaces the IT admin account takeover

Figure 7: Example of a client type device involved in extensive administrative RDP and SMB activity, as well as data uploads to Dropbox (this upload to Dropbox occurs few seconds before file encryption begins)

REvil vs AI

This Sodinokibi ransomware attack slipped under the radar of a range of traditional tools deployed by the retail organization. However, despite the threat dwelling in the retail organization’s digital environment for over a month, and REvil using local tools to blend in to regular traffic, from Darktrace’s perspective these actions were noisy in comparison to the organization’s normal ‘pattern of life’, setting off a series of alerts and investigations.

Darktrace’s Cyber AI Analyst was able to autonomously investigate nearly every attack phase of the ransomware. The technology works around the clock, without requiring training or time off, and can often reduce hours or days of incident response into just minutes, reducing time to triage by up to 92% and augmenting the capabilities of the human security team.

Thanks to Darktrace analyst Joel Lee for his insights on the above threat find.

Learn more about Cyber AI Analyst

Darktrace model detections:

  • Anomalous Connection / Active Remote Desktop Tunnel
  • Anomalous Connection / Data Sent To New External Device
  • Anomalous Connection / Data Sent to Rare Domain
  • Anomalous Connection / High Volume of New or Uncommon Service Control
  • Anomalous Connection / SMB Enumeration
  • Anomalous Connection / Uncommon 1 GiB Outbound
  • Anomalous Connection / Unusual Admin RDP Session
  • Anomalous Connection / Unusual Admin SMB Session
  • Anomalous File / Internal / Additional Extension Appended to SMB File
  • Anomalous Server Activity / Anomalous External Activity from Critical Network Device
  • Compliance / SMB Drive Write
  • Compliance / Possible Tor Usage
  • Compromise / Ransomware / Ransom or Offensive Words Written to SMB
  • Compromise / Ransomware / Suspicious SMB Activity
  • Device / ICMP Address Scan
  • Device / Multiple Lateral Movement Model Breaches
  • Device / Network Scan
  • Device / New or Uncommon WMI Activity
  • Device / New or Unusual Remote Command Execution
  • Device / RDP Scan
  • Device / Suspicious Network Scan Activity
  • Unusual Activity / Enhanced Unusual External Data Transfer
  • Unusual Activity / Unusual Internal Connections
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
Max Heinemeyer
Global Field CISO

More in this series

No items found.

Blog

/

/

August 21, 2026

AI Agents: Securing the Path from Intent to Action

Photograph of AI data centerDefault blog imageDefault blog image

The UK’s National Cyber Security Centre (NCSC) recently published guidance on managing the cyber risk of agentic AI. While the document is framed as interim advice as more formal guidance is developed, the framing reflects the current state of the industry: organizations are already deploying agents into production environments while standards, controls, and operating models for autonomous systems remain unsettled. Governance is evolving alongside adoption rather than preceding it, a reality which underscores the importance of robust controls.  

The NCSC’s guidance recommends aligning controls to an agent's level of autonomy, assigning distinct identities, limiting permissions, constraining access to systems and data, monitoring activity, maintaining human oversight, and preserving the ability to intervene when necessary. Most of these recommendations will sound familiar to security teams. The challenge is not the novelty of the controls. It is the type of system those controls now need to govern.

The shift from model security to agent security

For several years, AI security discussions have focused heavily on models. Can a model be manipulated? Jailbroken? Trusted? Can it expose information it should not? Those questions remain important, but they capture only part of the problem. A model generating text is one thing. A system connected to identities, applications, tools, workflows, and business data is another.

The difference becomes clearer when comparing a chatbot that answers questions with an agent that can retrieve customer records, update tickets, invoke tools, trigger workflows, and interact with external systems. The underlying model may be identical. Its access is not. The security question begins to shift from what the model knows to what the system can do.

The same theme appears in the Five Eyes statement released earlier this year, describing AI as a force multiplier that is accelerating both offensive and defensive cyber operations. The NCSC guidance explores what that reality looks like when autonomous systems begin operating inside enterprise environments.

Securing AI agents in operation

The NCSC spends relatively little time debating model behavior and considerably more time discussing identity, permissions, monitoring, oversight, containment, and response. Agents are treated as participants within an environment rather than isolated pieces of technology.  

That's broadly consistent with how we think about the problem at Darktrace.

An agent should not be treated as an extension of a user account. It develops its own behavioral patterns. It accesses systems, interacts with data, invokes tools, and moves across workflows in ways that can be observed independently. Understanding what an agent is permitted to do matters. Understanding how it actually behaves once deployed, and whether that behavior aligns with business intent, matters just as much.

Identity provides an obvious example. The NCSC recommends assigning distinct identities to agents rather than allowing them to disappear into surrounding human or service accounts. Most importantly, assigning agents distinct identities enables independent behavioral monitoring.

Development assumptions vs. real-world behavior

The same principle extends to monitoring. NCSC guidance places agent activity within normal security operations rather than treating it as a separate AI governance function. Many of the controls described are put in place before an agent begins operating. Sandboxing, credential design, approval workflows and human oversight all reflect judgments about how the system is expected to behave and what risks it is likely to create.

Actual use may challenge those assumptions. Access patterns change. Workflows expand. Systems begin interacting with resources they have never touched before. Processes that appeared reasonable during design behave differently in production. Human oversight requirements may turn out to be either excessive or inadequate once the system is operating at scale and operating within the context of unique business processes.

The Five Eyes statement points to a similar issue: organizations need confidence that controls continue to work as intended once systems are exposed to real users, data, tools and operational pressures. Often, the question is not whether an agent is technically allowed to perform an action, but whether its behavior remains consistent with the role it was intended to play.

Monitoring and governance of AI agents go hand-in-hand

This problem is exactly why monitoring and governance should be treated as part of the same process. Governance sets the initial parameters for deployment, while monitoring provides evidence about whether those parameters remain appropriate. That evidence should, in turn, inform changes to permissions, controls and oversight.

This matters increasingly as autonomous systems are integrated into business processes. The relevant risk is shaped not only by the model or agent itself, but by what it can access, what actions it can take, and how its behavior changes in practice.

Developing continuous oversight of AI agent behavior

The implication is clear: governance cannot end at deployment. Organizations need a way to understand how agents behave after deployment, test whether controls remain appropriate, and adjust them as conditions change. That requires visibility not just into technical activity, but into whether that activity makes sense in the context of the business process the agent is intended to support.

This is where business-centric behavioral security can become critical. Risk does not emerge from the model itself: it emerges from the actions an autonomous system takes within the enterprise and the downstream consequences of those actions.  

An agent can operate exactly as intended and still create risk if it accesses sensitive information in an unexpected context, exercises permissions in ways that create unintended exposure, or influences business processes in ways that were not anticipated during design and review.

Traditional governance vs. behavioral analytics

Traditional governance frameworks provide assurance at a point in time. Behavioral security can provide ongoing visibility into how autonomous systems interact with the organization they are meant to serve. Rather than focusing exclusively on model performance or policy compliance, organizations need to understand whether an agent's behavior aligns with business intent, operational expectations, and acceptable risk tolerances as conditions change.

As enterprises move from isolated AI deployments to interconnected ecosystems of agents, visibility into behavior becomes as important as visibility into code. Governance determines what an autonomous system is permitted to do. Behavioral analytics helps determine what it is doing, what business outcomes it is producing, and whether those outcomes remain aligned with the organization's objectives.

[related-resource]

Continue reading
About the author
Margaret Cunningham, PhD
VP, Security & AI Strategy, Field CISO

Blog

/

/

August 19, 2026

When AI Becomes the Lure: A Fake Gemini Installer Delivers Vidar

Default blog imageDefault blog image

Key takeaways

  • Darktrace observed a customer download a fake Google Gemini installer hosted on Google Colab, resulting in the execution of the Vidar information stealer.
  • Darktrace identified the compromise through behavioral indicators, including suspicious process activity, anomalous network communications, and indicators of credential theft, before autonomously containing the threat.
  • The incident highlights how threat actors are increasingly exploiting trusted platforms and a growing interest in AI tools to distribute malware through seemingly legitimate software acquisition workflows.

The Growing Abuse of Generative AI

As organizations are increasingly adopting generative AI tools into their daily workflows, attackers are adapting their distribution methods accordingly too. As part of their day-to-day work, users are now searching for AI assistants, programming tools, browser extensions, desktop applications, and productivity integrations.

Recent reports have highlighted campaigns that use fake AI software and AI-related installers to distribute malware and steal credentials [1]. Researchers have documented campaigns that exploit fake AI-themed websites and services to distribute information stealers and backdoors [2]. Security researchers have also observed attackers disguising malware as legitimate installers for AI software to increase the likelihood of victim interaction and execution [3].

In July 2026, Darktrace observed one such case within a customer environment in the Europe, Middle East and Africa (EMEA) region, where attackers used a fake generative AI installer to deliver the prolific information stealer Vidar. This incident highlights how threat actors are exploiting interest in AI services to distribute established malware using increasingly convincing social engineering techniques.

How a Fake Gemini Installer Delivered Vidar

Initial Access: From Search Result to Malware Download

Unlike many malware campaigns that begin with a phishing email, this activity appears to have originated from a user searching for and downloading software.

Darktrace first observed unusual activity on the customer network after a suspicious executable file was launched from a user’s Download folder. Further investigation revealed that the file purported to be a Google Gemini installer and was named “Download_Google_Gemini_For_Windows.exe”.

During the initial analysis, it was noted that the top search result for the suspicious filename associated pointed to a file hosted on Google Colab, a cloud-based Jupyter notebook platform, commonly used by developers, researchers, and data scientists to run code and machine learning workloads through a web browser. By leveraging another trusted Google platform, the attacker increased the likelihood that users would perceive the download as legitimate, making the lure more convincing to those searching for Gemini-related software.

Figure 1: The Google Colab page containing a download prompt for the fake Google Gemini installer.

Further investigation of the Google Colab page revealed that the download prompt redirected users to a secondary site, hxxps://micronsoftwares[.]com, which posed as a "Windows Software Hub" download page and offered the fake Gemini installer for download.

Figure 2: The secondary website posing as a "Windows Software Hub" download page, which likely hosted the fake Gemini installer.

While the investigation did not uncover any HTTP or file-download telemetry data that conclusively identified the download source, SSL communication sessions with Google Colab were detected immediately before the suspicious file was executed. The timing of these connections suggests that the user interacted with the Colab resource before being redirected to the secondary site from which the executable was downloaded.

The user was not simply tricked into opening an email attachment; instead, the attacker embedded malicious content into a process many users would consider entirely legitimate: searching for and downloading software associated with a trusted platform.

Weaponizing Trusted Platforms

At the time of review (July 15, 2026), Darktrace's Threat Research team confirmed that the Google Colab page was still active and prompting users to download a ZIP archive containing the binary file.

The archive also appeared to contain a README file instructing users to run the binary file with administrator privileges and add it to their antivirus software’s exception lists. These instructions suggest that the campaign relied heavily on social engineering, convincing users to take actions that would facilitate malware execution and potentially bypass security checks.

The use of a legitimate platform also complicates the user’s decision-making. Downloads associated with a trusted service are often perceived as less suspicious than those hosted on unfamiliar domains. When combined with the branding of a widely used AI tool, the lure becomes even more convincing.

Malware Analysis

Darktrace’s Threat Research team identified the executable file as the information-stealing malware Vidar. Analysis revealed that the binary file was a newer Go-compiled variant that communicated with Telegram-based infrastructure. Darktrace’s researchers also identified dtm[.]kijangturbo88[.]top as a command-and-control (C2) endpoint associated with the activity. While the malware itself was not novel, the lure and delivery mechanism was.

For a deeper look at the information stealer, see Darktrace’s 2023 analysis of Vidar.

Figure 3: Darktrace’s detection of the unusual outbound connection associated with the fake Gemini installer.

Shortly after execution, the process established communications with the external IP address 91.98.98[.]86 via port 443, directly linking the executable to suspicious network activity observed on the device. Subsequent open-source intelligence (OSINT) analysis of the revealed multiple malicious associations [5].

Additional Darktrace detections included unusual SSL activity from the affected device. Analysis of related SSL telemetry identified 91.98.111[.]49 as additional infrastructure associated  with the activity [6].

Subsequent alerts from the customer's Microsoft Defender for Endpoint integration later confirmed activity consistent with the theft of browser credentials and other sensitive data from the affected endpoint.

Taken together, these detections provided a clear picture of the attack, from the execution of a suspicious file and unusual network connections to indicators of C2 activity and credential theft.

Figure 4: Darktrace’s detection of anomalous activity following the execution of the fake Gemini installer, seen in the Model Alert Event Log.

Darktrace's Autonomous Response

Following the detection, Darktrace’s Autonomous Response took immediate containment action, including blocking communication with suspicious external infrastructure, including 91.98.98[.]86, and quarantining the compromised device.

Despite the apparent legitimacy of the activity, with the installer hosted on a trusted platform and resembling a routine software download, Darktrace was able to detect and contain the attack because the device's behavior deviated from its normal pattern.

Figure 5: Automated containment actions implemented by Darktrace's Autonomous Response following the detection of activity associated with the fake Gemini installer.

Conclusion

This investigation highlights how threat actors continue to adapt established malware delivery techniques to emerging technology trends. While the malware itself was not new, the distribution method was. By disguising Vidar as a Google Gemini installer and hosting the malicious content on a trusted platform, the attack aligned its lure with a growing behavioral trend: users actively searching for AI tools and services as part of their day-to-day work.

Although fake installers are not a new phenomenon, the rapid rise of generative AI has created new opportunities for threat actors. Rather than relying solely on traditional delivery methods, attackers can now target users who are actively searching for AI applications. As AI adoption continues to accelerate across enterprise environments, organizations should remain alert to campaigns that exploit this interest through fake applications, malicious websites, manipulated search results, the misuse of trusted platforms, and AI-themed social engineering.

Credit to Rushanth Ramanathan (Cyber Analyst) Joanna Ng (Detection Engineer)

Edited by Ryan Traill (Content Manager)

Appendices

Darktrace Model Detections

  • Security Integration / C2 Activity and Integration Detection
  • Endpoint / New Suspicious Executable Launched
  • Endpoint / Process Connection / Unusual Connection from New Process
  • Anomalous Connection / Rare External SSL Self-Signed
  • Security Integration / High Severity Integration Detection
  • Antigena / Network / Significant Anomaly /  Antigena Significant Security Integration and Network Activity Block

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

List of Indicators of Compromise (IoCs)

IoC Type Description
Download_Google_Gemini_For_Windows.exe File Fake Gemini-themed installer observed during the investigation.
GoogleAppInstaller.exe File Related executable identified through endpoint telemetry.
91.98.98[.]86 IP Address External destination contacted by the malicious executable.
91.98.111[.]49 IP Address Related infrastructure identified through SSL certificate pivoting.
dtm[.]kijangturbo88[.]top Domain Command-and-control endpoint identified during malware analysis.
1e13c2c9eac72daf63fd00a9946878949e159ae6ec51b54ec64f942d79d61913 SHA256 Malware sample associated with the fake Gemini installer.

MITRE ATT@CK Mapping


MITRE ATT&CK Mapping Tactic Technique
Initial Access T1204 User Execution
Execution T1204.002 User Execution: Malicious File
Defence Evasion T1036 Masquerading
Credential Access T1555 Credentials from Password Stores
Credential Access T1555.003 Credentials from Web Browsers
Command and Control T1071 Application Layer Protocol
Exfiltration T1041 Exfiltration Over C2 Channel
Continue reading
About the author
Rushanth Ramanathan
Cyber Analyst
Your data. Our AI.
Elevate your network security with Darktrace AI