Blog
/
/
July 8, 2021

Minimizing the REvil Impact Delivered via Kaseya Servers

Ransomware group REvil recently infiltrated Managed Service Providers for 1,500+ companies. See how Darktrace's autonomous response protected customer data.
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 imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
08
Jul 2021

As the USA prepared for a holiday weekend ahead of the Fourth of July, the ransomware group REvil were leveraging a vulnerability in Kaseya software to attack Managed Service Providers (MSPs) and their downstream customers. At least 1,500 companies appear to have been affected, even ones with no direct relationship to Kaseya.

At the time of writing, it appears that a zero-day vulnerability was used to gain access to the Kaseya VSA servers, before deploying ransomware on the endpoints managed by those VSA servers. This modus operandi vastly differs from previous ransomware campaigns which have traditionally been human-operated, direct intrusions.

The analysis below offers Darktrace’s insights into the campaign by looking at a real-life example. It highlights how Self-Learning AI detected the ransomware attack, and how Antigena protected customer data on the network from being encrypted.

Dissecting REvil ransomware from the network perspective

Antigena detected the first signs of ransomware on the network as soon as encryption had begun. The graphic below illustrates the start of the ransomware encryption over SMB shares. When the graphic was taken, the attack was happening live and had never been seen before. As it was a novel threat, Darktrace stopped the network encryption without any static signatures or rules.

Figure 1: Darktrace detects encryption from the infected device

The ransomware began to take action at 11:08:32, shown by the ‘SMB Delete Success’ from the infected laptop to an SMB server. While the laptop sometimes reads files on that SMB server, it never deletes these types of files on this particular file share, so Darktrace detected this activity as new and unusual.

Simultaneously, the infected laptop created the ransom note ‘943860t-readme.txt’. Again, the ‘SMB Write Success’ to the SMB server was new activity – and crucially, Darktrace did not look for a static string or a known ransom note. Instead – by previously learning the ‘normal’ behavior of every entity, peer group, and the overall enterprise – it identified that the activity was unusual and new for this organization and device.

By detecting and correlating these subtle anomalies, Darktrace identified this as the earliest stages of ransomware encryption on the network and Antigena took immediate action.

Figure 2: Snapshot of Antigena’s actions

Antigena took two precise steps:

  1. Enforce ‘pattern of life’ for five minutes: This prevented the infected laptop from making any connections that were new or unusual. In this case, it prevented any further new SMB encryption activity.
  2. Quarantine device for 24 hours: Usually, Antigena would not take such drastic action, but it was clear that this activity closely resembled ransomware behavior, so Antigena decided to quarantine the device on the network completely to prevent it from doing any further damage.

For several minutes, the infected laptop kept trying to connect to other internal devices via SMB to continue the encryption activity. It was blocked by Antigena at every stage, limiting the spread of the attack and mitigating any damage posed via the network encryption.

Figure 3: End of the attack

On a technical level, Antigena delivered the blocking mechanisms via integrations with native security controls such as existing firewalls, or by taking action itself to disrupt the connections.

The below graphic shows the ‘pattern of life’ for all network connections for the infected laptop. The three red dots represent Darktrace’s detections and pinpoint the exact moment in time when REvil ransomware was installed on the laptop. The graphic also shows an abrupt stop to all network communication as Antigena quarantined the device.

Figure 4: Network connections from the compromised laptop

Attacks will always get in

During the incident, part of the encryption happened locally on the endpoint device, which Darktrace had no visibility over. Furthermore, the Internet-facing Kaseya VSA server that was initially compromised was not visible to Darktrace in this case.

Nevertheless, Self-Learning AI detected the infection as soon as it reached the network. This shows the importance of being able to defend against active ransomware within the enterprise. Organizations cannot rely solely on a single layer of defense to keep threats out. An attacker will always – eventually – breach your environment. Defense therefore needs to change its approach towards detecting and mitigating damage once an adversary is inside.

Many cyber-attacks succeed in bypassing endpoint controls and begin to spread aggressively in corporate environments. Autonomous Response can provide resilience in such cases, even for novel campaigns and new strains of malware.

Thanks to Self-Learning AI, ransomware from the REvil attack could not perform any encryption over the network, and files available on that network were saved. This included the organization’s critical file servers which did not have Kaseya installed and thus did not receive the initial payload via the malicious update directly. By interrupting the attack as it happened, Antigena prevented thousands of files on network shares from being encrypted.

Further observations

Data exfiltration

In contrast to other REvil intrusions Darktrace has caught in the past, no data exfiltration has been observed. This is interesting as it differs from the general trend this last year where cyber-criminal groups generally focus more on the exfiltration of data to hold their victims to ransom, in response to companies becoming better with backups.

Bitcoin

REvil has demanded a total payment of $70 million in Bitcoin. For a group that tries to maximize their profits, this seems odd for two reasons:

  1. How do they expect a single entity to collect $70 million from potentially thousands of affected organizations? They must be aware of the massive logistical challenges behind this, even if they do expect Kaseya to act as a focal point for collecting the money.
  2. Since DarkSide lost access to most of the Colonial Pipeline ransom, ransomware groups have shifted to demanding payments in Monero rather than Bitcoin. Monero appears to be more difficult to track for law enforcement agencies. The fact REvil are using Bitcoin, a more traceable cryptocurrency, appears counter-productive to their usual goal of maximizing profits.

Ransomware-as-a-Service (RaaS)

Darktrace also noticed that other, more traditional ‘big game hunting’ REvil ransomware operations took place over the same weekend. This is not surprising as REvil is running a RaaS model, so it is likely some affiliate groups continued their regular big game hunting attacks while the Kaseya supply chain attack was underway.

Unpredictable is not undefendable

The weekend of the Fourth of July experienced major supply chain attacks against Kaseya and separately, against California-based distributor Synnex. Threats are coming from every direction – leveraging zero-days, social engineering tactics, and other advanced tools.

The case study above demonstrates how self-learning technology detects such attacks and minimizes the damage. It functions as a crucial part of defense-in-depth when other layers – such as endpoint protection, threat intelligence or known signatures and rules – fail to detect unknown threats.

The attack happened in milliseconds, faster than any human security team could react. Autonomous Response has proven invaluable in outpacing this new generation of machine-speed threats. It keeps thousands of organizations safe around the world, around the clock, stopping an attack every second.

Darktrace model detections

  • Compromise / Ransomware / Suspicious SMB Activity
  • Compromise / Ransomware / Suspicious SMB File Extension
  • Compromise / Ransomware / Ransom or Offensive Words Written to SMB
  • Compromise / Ransomware / Ransom or Offensive Words Read from SMB
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

/

Email

/

May 1, 2026

How email-delivered prompt injection attacks can target enterprise AI – and why it matters

Default blog imageDefault blog image

What are email-delivered prompt injection attacks?

As organizations rapidly adopt AI assistants to improve productivity, a new class of cyber risk is emerging alongside them: email-delivered AI prompt injection. Unlike traditional attacks that target software vulnerabilities or rely on social engineering, this is the act of embedding malicious or manipulative instructions into content that an AI system will process as part of its normal workflow. Because modern AI tools are designed to ingest and reason over large volumes of data, including emails, documents, and chat histories, they can unintentionally treat hidden attacker-controlled text as legitimate input.  

At Darktrace, our analysis has shown an increase of 90% in the number of customer deployments showing signals associated with potential prompt injection attempts since we began monitoring for this type of activity in late 2025. While it is not always possible to definitively attribute each instance, internal scoring systems designed to identify characteristics consistent with prompt injection have recorded a growing number of high-confidence matches. The upward trend suggests that attackers are actively experimenting with these techniques.

Recent examples of prompt injection attacks

Two early examples of this evolving threat are HashJack and ShadowLeak, which illustrate prompt injection in practice.

HashJack is a novel prompt injection technique discovered in November 2025 that exploits AI-powered web browsers and agentic AI browser assistants. By hiding malicious instructions within the URL fragment (after the # symbol) of a legitimate, trusted website, attackers can trick AI web assistants into performing malicious actions – potentially inserting phishing links, fake contact details, or misleading guidance directly into what appears to be a trusted AI-generated output.

ShadowLeak is a prompt injection method to exfiltrate PII identified in September 2025. This was a flaw in ChatGPT (now patched by OpenAI) which worked via an agent connected to email. If attackers sent the target an email containing a hidden prompt, the agent was tricked into leaking sensitive information to the attacker with no user action or visible UI.

What’s the risk of email-delivered prompt injection attacks?

Enterprise AI assistants often have complete visibility across emails, documents, and internal platforms. This means an attacker does not need to compromise credentials or move laterally through an environment. If successful, they can influence the AI to retrieve relevant information seamlessly, without the labor of compromise and privilege escalation.

The first risk is data exfiltration. In a prompt injection scenario, malicious instructions may be embedded within an ordinary email. As in the ShadowLeak attack, when AI processes that content as part of a legitimate task, it may interpret the hidden text as an instruction. This could result in the AI disclosing sensitive data, summarizing confidential communications, or exposing internal context that would otherwise require significant effort to obtain.

The second risk is agentic workflow poisoning. As AI systems take on more active roles, prompt injection can influence how they behave over time. An attacker could embed instructions that persist across interactions, such as causing the AI to include malicious links in responses or redirect users to untrusted resources. In this way, the attacker inserts themselves into the workflow, effectively acting as a man-in-the-middle within the AI system.

Why can’t other solutions catch email-delivered prompt injection attacks?

AI prompt injection challenges many of the assumptions that traditional email security is built on. It does not fit the usual patterns of phishing, where the goal is to trick a user into clicking a link or opening an attachment.  

Most security solutions are designed to detect signals associated with user engagement: suspicious links, unusual attachments, or social engineering cues. Prompt injection avoids these indicators entirely, meaning there are fewer obvious red flags.

In this case, the intention is actually the opposite of user solicitation. The objective is simply for the email to be delivered and remain in the inbox, appearing benign and unremarkable. The malicious element is not something the recipient is expected to engage with, or even notice.

Detection is further complicated by the nature of the prompts themselves. Unlike known malware signatures or consistent phishing patterns, injected prompts can vary widely in structure and wording. This makes simple pattern-matching approaches, such as regex, unreliable. A broad rule set risks generating large numbers of false positives, while a narrow one is unlikely to capture the diversity of possible injections.

How does Darktrace catch these types of attacks?

The Darktrace approach to email security more generally is to look beyond individual indicators and assess context, which also applies here.  

For example, our prompt density score identifies clusters of prompt-like language within an email rather than just single occurrences. Instead of treating the presence of a phrase as a blocking signal, the focus is on whether there is an unusual concentration of these patterns in a way that suggests injection. Additional weighting can be applied where there are signs of obfuscation. For example, text that is hidden from the user – such as white font or font size zero – but still readable by AI systems can indicate an attempt to conceal malicious prompts.

This is combined with broader behavioral signals. The same communication context used to detect other threats remains relevant, such as whether the content is unusual for the recipient or deviates from normal patterns.

Ask your email provider about email-delivered AI prompt injection

Prompt injection targets not just employees, but the AI systems they rely on, so security approaches need to account for both.

Though there are clear indications of emerging activity, it remains to be seen how popular prompt injection will be with attackers going forward. Still, considering the potential impact of this attack type, it’s worth checking if this risk has been considered by your email security provider.

Questions to ask your email security provider

  • What safeguards are in place to prevent emails from influencing AI‑driven workflows over time?
  • How do you assess email content that’s benign for a human reader, but may carry hidden instructions intended for AI systems?
  • If an email contains no links, no attachments, and no social engineering cues, what signals would your platform use to identify malicious intent?

Visit the Darktrace / EMAIL product hub to discover how we detect and respond to advanced communication threats.  

Learn more about securing AI in your enterprise.

Continue reading
About the author
Kiri Addison
Senior Director of Product

Blog

/

AI

/

April 30, 2026

Mythos vs Ethos: Defending in an Era of AI‑Accelerated Vulnerability Discovery

mythos vulnerability discoveryDefault blog imageDefault blog image

Anthropic’s Mythos and what it means for security teams

Recent attention on systems such as Anthropic Mythos highlights a notable problem for defenders. Namely that disclosure’s role in coordinating defensive action is eroding.

As AI systems gain stronger reasoning and coding capability, their usefulness in analyzing complex software environments and identifying weaknesses naturally increases. What has changed is not attacker motivation, but the conditions under which defenders learn about and organize around risk. Vulnerability discovery and exploitation increasingly unfold in ways that turn disclosure into a retrospective signal rather than a reliable starting point for defense.

Faster discovery was inevitable and is already visible

The acceleration of vulnerability discovery was already observable across the ecosystem. Publicly disclosed vulnerabilities (CVEs) have grown at double-digit rates for the past two years, including a 32% increase in 2024 according to NIST, driven in part by AI even prior to Anthropic’s Mythos model. Most notably XBOW topped the HackerOne US bug bounty leaderboard, marking the first time an autonomous penetration tester had done so.  

The technical frontier for AI capabilities has been described elsewhere as jagged, and the implication is that Mythos is exceptional but not unique in this capability. While Mythos appears to make significant progress in complex vulnerability analysis, many other models are already able to find and exploit weaknesses to varying degrees.  

What matters here is not which model performs best, but the fact that vulnerability discovery is no longer a scarce or tightly bounded capability.

The consequence of this shift is not simply earlier discovery. It is a change in the defender-attacker race condition. Disclosure once acted as a rough synchronization point. While attackers sometimes had earlier knowledge, disclosure generally marked the moment when risk became visible and defensive action could be broadly coordinated. Increasingly, that coordination will no longer exist. Exploitation may be underway well before a CVE is published, if it is published at all.

Why patch velocity alone is not the answer

The instinctive response to this shift is to focus on patching faster, but treating patch velocity as the primary solution misunderstands the problem. Most organizations are already constrained in how quickly they can remediate vulnerabilities. Asset sprawl, operational risk, testing requirements, uptime commitments, and unclear ownership all limit response speed, even when vulnerabilities are well understood.

If discovery and exploitation now routinely precede disclosure, then patching cannot be the first line of defense. It becomes one necessary control applied within a timeline that has already shifted. This does not imply that organizations should patch less. It means that patching cannot serve as the organizing principle for defense.

Defense needs a more stable anchor

If disclosure no longer defines when defense begins, then defense needs a reference point that does not depend on knowing the vulnerability in advance.  

Every digital environment has a behavioral character. Systems authenticate, communicate, execute processes, and access resources in relatively consistent ways over time. These patterns are not static rules or signatures. They are learned behaviors that reflect how an organization operates.

When exploitation occurs, even via previously unknown vulnerabilities, those behavioral patterns change.

Attackers may use novel techniques, but they still need to gain access, create processes, move laterally, and will ultimately interact with systems in ways that diverge from what is expected. That deviation is observable regardless of whether the underlying weakness has been formally named.

In an environment where disclosure can no longer be relied on for timing or coordination, behavioral understanding is no longer an optional enhancement; it becomes the only consistently available defensive signal.

Detecting risk before disclosure

Darktrace’s threat research has consistently shown that malicious activity often becomes visible before public disclosure.

In multiple cases, including exploitation of Ivanti, SAP NetWeaver, and Trimble Cityworks, Darktrace detected anomalous behavior days or weeks ahead of CVE publication. These detections did not rely on signatures, threat intelligence feeds, or awareness of the vulnerability itself. They emerged because systems began behaving in ways that did not align with their established patterns.

This reflects a defensive approach grounded in ‘Ethos’, in contrast to the unbounded exploration represented by ‘Mythos’. Here, Mythos describes continuous vulnerability discovery at speed and scale. Ethos reflects an understanding of what is normal and expected within a specific environment, grounded in observed behavior.

Revisiting assume breach

These conditions reinforce a principle long embedded in Zero Trust thinking: assume breach.

If exploitation can occur before disclosure, patching vulnerabilities can no longer act as the organizing principle for defense. Instead, effective defense must focus on monitoring for misuse and constraining attacker activity once access is achieved. Behavioral monitoring allows organizations to identify early‑stage compromise and respond while uncertainty remains, rather than waiting for formal verification.

AI plays a critical role here, not by predicting every exploit, but by continuously learning what normal looks like within a specific environment and identifying meaningful deviation at machine speed. Identifying that deviation enables defenders to respond by constraining activity back towards normal patterns of behavior.

Not an arms race, but an asymmetry

AI is often framed as fueling an arms race between attackers and defenders. In practice, the more important dynamic is asymmetry.

Attackers operate broadly, scanning many environments for opportunities. Defenders operate deeply within their own systems, and it’s this business context which is so significant. Behavioral understanding gives defenders a durable advantage. Attackers may automate discovery, but they cannot easily reproduce what belonging looks like inside a particular organization.

A changed defensive model

AI‑accelerated vulnerability discovery does not mean defenders have lost. It does mean that disclosure‑driven, patch‑centric models no longer provide a sufficient foundation for resilience.

As vulnerability volumes grow and exploitation timelines compress, effective defense increasingly depends on continuous behavioral understanding, detection that does not rely on prior disclosure, and rapid containment to limit impact. In this model, CVEs confirm risk rather than define when defense begins.

The industry has already seen this approach work in practice. As AI continues to reshape both offense and defense, behavioral detection will move from being complementary to being essential.

Continue reading
About the author
Andrew Hollister
Principal Solutions Engineer, Cyber Technician
Your data. Our AI.
Elevate your network security with Darktrace AI