ブログ
/
Network
/
December 23, 2021

9 Stages of Ransomware & How AI Responds

Discover the 9 stages of ransomware attacks and how AI responds at each stage. Learn how you can protect your business from cyber threats.
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
Dan Fein
VP, Product
Default blog image
23
Dec 2021

Ransomware gets its name by commandeering and holding assets ransom, extorting their owner for money in exchange for discretion and full cooperation in returning exfiltrated data and providing decryption keys to allow business to resume.

Average ransom demands are skyrocketing, rising to $5.3 million in 2021, a 518% increase from the previous year. But the cost of recovering from a ransomware attack typically far exceeds the ransom payments: the average downtime after a ransomware attack is 21 days; and 66% of ransomware victims report a significant loss of revenue following a successful attack.

In this series, we break down this huge topic step by step. Ransomware is a multi-stage problem, requiring a multi-stage solution that autonomously and effectively contains the attack at any stage. Read on to discover how Self-Learning AI and Autonomous Response stops ransomware in its tracks.

1. Initial intrusion (email)

Initial entry – the first stage of a ransomware attack – can be achieved through RDP brute-forcing (exposed Internet service), malicious websites and drive-by downloads, an insider threat with company credentials, system and software vulnerabilities, or any number of other attack vectors.

But the most common initial attack vector is email. An organization’s biggest security weakness is often their people – and attackers are good at finding ways of exploiting this. Well-researched, targeted, legitimate-looking emails are aimed at employees attempting to solicit a reaction: a click of a link, an opening of an attachment, or persuading them to divulge credentials or other sensitive information.

Gateways: Stops what has been seen before

Most conventional email tools rely on past indicators of attack to try and spot the next threat. If an email comes in from a blocklisted IP address or email domain, and uses known malware that has previously been seen in the wild, the attack may be blocked.

But the reality is, attackers know the majority of defenses take this historical approach, and so constantly update their attack infrastructure to bypass these tools. By buying new domains for a few pennies each, or creating bespoke malware with just small adaptions to the code, they can outpace and outsmart the legacy approach taken by a typical email gateway.

Real-world example: Supply chain phishing attack

By contrast, Darktrace’s evolving understanding of ‘normal’ for every email user in the organization enables it to detect subtle deviations that point to a threat – even if the sender or any malicious contents of the email are unknown to threat intelligence. This is what enabled the technology to stop an attack that recently targeted McLaren Racing, with emails sent to a dozen employees in the organization each containing a malicious link. This possible precursor to ransomware bypassed conventional email tools – largely because it was sent from a known supplier – however Darktrace recognized the account hijack and held the email back.

Figure 1: A snapshot of Darktrace’s Threat Visualizer surfacing the malicious email

Read the full case study

2. Initial intrusion (server-side)

With organizations rapidly expanding their Internet-facing perimeter, this increased attack surface has paved the way for a surge in brute-force and server-side attacks.

A number of vulnerabilities against such Internet-facing servers and systems have been disclosed this year, and for attackers, targeting and exploiting public-facing infrastructure is easier than ever – scanning the Internet for vulnerable systems is made simple with tools like Shodan or MassScan.

Attackers may also achieve initial intrusion via RDP brute-forcing or stolen credentials, with attackers often reusing legitimate credentials from previous data dumps. This has much higher precision and is less noisy than a classic brute-force attack.

A lot of ransomware attacks use RDP as an entry vector. This is part of a wider trend of ‘Living off the Land’: using legitimate off-the-shelf tools (abusing RDP, SMB1 protocol, or various command line tools WMI or Powershell) to blur detection and attribution by blending in with typical administrator activity. Ensuring that backups are isolated, configurations are hardened, and systems are patched is not enough – real-time detection of every anomalous action is needed.

Antivirus, firewalls and SIEMs

In cases of malware downloads, endpoint antivirus will detect these if, and only if, the malware has been seen and fingerprinted before. Firewalls typically require configuration on a per-organization basis, and often need to be modified based on the needs of the business. If the attack hits the firewall where a rule or signature does not match it, again, it will bypass the firewall.

SIEM and SOAR tools also look for known malware being downloaded, leverage pre-programmed rules and use pre-programmed responses. While these tools do look for patterns, these patterns are defined in advance, and this approach relies on a new attack to have sufficiently similar traits to attacks that have been seen before.

Real-world example: Dharma ransomware

Darktrace detected a targeted Dharma ransomware attack against a UK organization exploiting an open RDP connection through Internet-facing servers. The RDP server began receiving a large number of incoming connections from rare IP addresses on the Internet. It is highly likely that the RDP credential used in this attack had been compromised at a previous stage – either via common brute-force methods, credential stuffing attacks, or phishing. Indeed, a technique growing in popularity is to buy RDP credentials on marketplaces and skip to initial access.

Figure 2: The model breaches that fired over the course of this attack, including anomalous RDP activity

Unfortunately, in this case, without Autonomous Response installed, the Dharma ransomware attack continued until its final stages, where the security team were forced into the heavy-handed and disruptive action of pulling the plug on the RDP server midway through encryption.

Read the full case study

3. Establish foothold and C2

Whether through a successful phish, a brute-force attack, or some other method, the attacker is in. Now, they make contact with the breached device(s) and establish a foothold.

This stage allows attackers to control subsequent stages of the attack remotely. During these command and control (C2) communications, further malware may also pass from the attacker to the devices. This helps them to establish an even greater foothold within the organization and readies them for lateral movement.

Attackers can adapt malware functionality with an assortment of ready-made plug-ins, allowing them to lie low inside the business undetected. More modern and sophisticated ransomware is able to adapt by itself to the surrounding environment, and operate autonomously, blending in to regular activity even when cut off from its command and control server. These ‘self-sufficient’ ransomware strains pose a big problem for traditional defenses reliant on stopping threats solely on the grounds of its malicious external connections.

Viewing connections in isolation vs understanding the business

Conventional security tools like IDS and firewalls tend to look at connections in isolation rather than in the context of previous and potentially relevant connections, making command and control very difficult to spot.

IDS and firewalls may block ‘known-bad’ domains or use some geo-blocking, but this is where an attacker would likely leverage new infrastructure.

These tools also don’t tend to analyze for things like the periodicity, such as whether a connection is beaconing at a regular or irregular interval, or the age and rarity of the domain in the context of the environment.

With Darktrace’s evolving understanding of the digital enterprise, suspicious C2 connections and the downloads which follow them are spotted, even when conducted using regular programs or methods. The AI technology correlates multiple subtle signs of threat – a small subset of which includes anomalous connections to young and/or unusual endpoints, anomalous file downloads, incoming remote desktop, and unusual data uploads and downloads.

Once they are detected as a threat, Darktrace's Autonomous Response halts these connections and downloads, while allowing normal business activity to continue.

Real-world example: WastedLocker attack

When a WastedLocker ransomware attack hit a US agricultural organization, Darktrace immediately detected the initial unusual SSL C2 activity (based on a combination of destination rarity, JA3 unusualness and frequency analysis). Antigena (on this occasion configured in passive mode, and therefore not granted permission to take autonomous action) suggested instantly blocking the C2 traffic on port 443 and parallel internal scanning on port 135.

Figure 3: The Threat Visualizer reveals the action Antigena would have taken

When beaconing was later observed to bywce.payment.refinedwebs[.]com, this time over HTTP to /updateSoftwareVersion, Antigena escalated its response by blocking the further C2 channels.

Figure 4: Antigena escalates its response

Read the full case study

4. Lateral movement

Once an attacker has established a foothold within an organization, they begin to increase their knowledge of the wider digital estate and their presence within it. This is how they will find and access the files which they will ultimately attempt to exfiltrate and encrypt. It begins reconnaissance: scanning the network; building up a picture of its component devices; identifying the location of the most valuable assets.

Then the attacker begins moving laterally. They infect more devices and look to escalate their privileges – for instance, by obtaining admin credentials – thereby increasing their control over the environment. Once they have obtained authority and presence within the digital estate, they can progress to the final stages of the attack.

Modern ransomware has built-in functions that allow it to search automatically for stored passwords and spread through the network. More sophisticated strains are designed to build themselves differently in different environments, so the signature is constantly changing and it’s harder to detect.

Legacy tools: A blunt response to known threats

Because they rely upon static rules and signatures, legacy solutions struggle to prevent lateral movement and privilege escalation without also impeding essential business operations. Whilst in theory, an organization leveraging firewalls and NAC internally with proper network segmentation and a perfect configuration could prevent cross-network lateral movement, maintaining a perfect balance between protective and disruptive controls is near impossible.

Some organizations rely on Intrusion Prevent Systems (IPS) to deny network traffic when known threats are detected in packets, but as with previous stages, novel malware will evade detection, and this requires the database to be constantly updated. These solutions also sit at the ingress/egress points, limiting their network visibility. An Intrusion Detection System (IDS) may sit out-of-line, but doesn’t have response capabilities.

A self-learning approach

Darktrace’s AI learns ‘self’ for the organization, enabling it to detect suspicious activity indicative of lateral movement, regardless of whether the attacker uses new infrastructure or ‘lives off the land’. Potential unusual activity that Darktrace detects includes unusual scanning activity, unusual SMB, RDP, and SSH activity. Other models that fire at this stage include:

  • Suspicious Activity on High-Risk Device
  • Numeric EXE in SMB Write
  • New or Uncommon Service Control

Autonomous Response then takes targeted action to stop the threat at this stage, blocking anomalous connections, enforcing the infected device’s ‘pattern of life’, or enforcing the group ‘pattern of life’ – automatically clustering devices into peer groups and preventing a device from doing anything its peer group hasn’t done.

Where malicious behavior persists, and only if necessary, Darktrace will quarantine an infected device.

Real-world example: Unusual chain of RDP connections

At an organization in Singapore, one compromised server led to the creation of a botnet, which began moving laterally, predominantly by establishing chains of unusual RDP connections. The server then started making external SMB and RPC connections to rare endpoints on the Internet, in an attempt to find further vulnerable hosts.

Other lateral movement activities detected by Darktrace included the repeated failing attempts to access multiple internal devices over the SMB file-sharing protocol with a range of different usernames, implying brute-force network access attempts.

Figure 5: Darktrace’s Cyber AI Analyst reveals suspicious TCP scanning followed by a suspicious chain of administrative RDP connections

Read the full case study

5. Data exfiltration

In the past, ransomware was simply about encrypting an operating system and network files.

In a modern attack, as organizations insure against malicious encryption by becoming increasingly diligent with data backups, threat actors have moved towards ‘double extortion’, where they exfiltrate key data and destroy backups before the encryption takes place. Exfiltrated data is used to blackmail organizations, with attackers threatening to publish sensitive information online or sell it on to the organization’s competitors if they are not paid.

Modern ransomware variants also look for cloud file storage repositories such as Box, Dropbox, and others.

Many of these incidents aren’t public, because if IP is stolen, organizations are not always legally required to disclose it. However, in the case of customer data, organizations are obligated by law to disclose the incident and face the additional burden of compliance files – and we’ve seen these mount in recent years (Marriot, $23.8 million; British Airways, $26 million; Equifax, $575 million). There’s also the reputational blow associated with having to inform customers that a data breach has occurred.

Legacy tools: The same old story

For those that have been following, the narrative by now will sound familiar: to stop a ransomware attack at this stage, most defenses rely on either pre-programmed definitions of 'bad' or have rules constructed to combat different scenarios put organizations in a risky, never-ending game of cat and mouse.

A firewall and proxy might block connections based on pre-programmed policies based on specific endpoints or data volumes, but it’s likely an attacker will ‘live off the land’ and utilize a service that is generally allowed by the business.

The effectiveness of these tools will vary according to data volumes: they might be effective for ‘smash and grab’ attacks using known malware, and without employing any defense evasion techniques, but are unlikely to spot ‘low and slow’ exfiltration and novel or sophisticated strains.

On the other hand, because by nature it involves a break from expected behavior, even less conspicuous, low and slow data exfiltration is detected by Darktrace and stopped with Darktrace's Autonomos Response. No confidential files are lost, and attackers are unable to extort a ransom payment through blackmail.

Real-world example: Unusual chain of RDP connections

It becomes more difficult to find examples of Darktrace stopping ransomware at these later stages, as the threat is usually contained before it gets this far. This is the double-edged sword of effective security – early containment makes for bad storytelling! However, we can see the effects of a double extortion ransomware attack on an energy company in Canada. The organization had the Enterprise Immune System but no Antigena, and without anyone actively monitoring Darktrace’s AI detections, the attack was allowed to unfold.

The attacker managed to connect to an internal file server and download 1.95TB of data. The device was also seen downloading Rclone software – an open-source tool, which was likely applied to sync data automatically to the legitimate file storage service pCloud. Following the completion of the data exfiltration, the device ‘serverps’ finally began encrypting files on 12 devices with the extension *.06d79000. As with the majority of ransomware incidents, the encryption happened outside of office hours – overnight in local time – to minimize the chance of the security team responding quickly.

Read the full details of the attack

It should be noted that the exact order of the stages 3–5 above is not set in stone, and varies according to attack. Sometimes data is exfiltrated and then there is further lateral movement, and additional C2 beaconing. This entire period is known as the ‘dwell time’. Sometimes it takes place over only a few days, other times attackers may persist for months, slowly gathering more intel and exfiltrating data in a ‘low and slow’ fashion so as to avoid detection from rule-based tools that are configured to flag any single data transfer over a certain threshold. Only through a holistic understanding of malicious activity over time can a technology spot this level of activity and allow the security team to remove the threat before it reaches the latter and most damaging stages of ransomware.

6. Data encryption

Using either symmetric encryption, asymmetric encryption, or a combination of the two, attackers attempt to render as much data unusable in the organization’s network as they can before the attack is detected.

As the attackers alone have access to the relevant decryption keys, they are now in total control of what happens to the organization’s data.

Pre-programmed response and disruption

There are many families of tools that claim to stop encryption in this manner, but each contain blind spots which enable a sophisticated attacker to evade detection at this crucial stage. Where they do take action, it is often highly disruptive, causing major shutdowns and preventing a business from continuing its usual operations.

Internal firewalls prevent clients from accessing servers, so once an attacker has penetrated to servers using any of the techniques outlined above, they have complete freedom to act as they want.

Similarly, antivirus tools look only for known malware. If the malware has not been detected until this point, it is highly unlikely the antivirus will act here.

Stopping encryption autonomously

Even if familiar tools and methods are used to conduct it, Autonomous Response can enforce the normal ‘pattern of life’ for devices attempting encryption, without using static rules or signatures. This action can be taken independently or via integrations with native security controls, maximizing the return on other security investments. With a targeted Autonomous Response, normal business operations can continue while encryption is prevented.

7. Ransom note

It is important to note that in the stages before encryption, this ransomware attack is not yet “ransomware”. Only at this stage does it gets its name.

A ransom note is deployed. The attackers request payment in return for a decryption key and threaten the release of sensitive exfiltrated data. The organization must decide whether to pay the ransom or lose their data, possibly to their competition or the public. The average demand made by ransomware threat actors rose in 2021 to $5.3 million, with meat processing company JBS paying out $11 million and DarkSide receiving over $90 million in Bitcoin payments following the Colonial Pipeline incident.

All of the stages up until this point represent a typical, traditional ransomware attack. But ransomware is shifting from indiscriminate encryption of devices to attackers targeting business disruption in general, using multiple techniques to hold their victims to ransom. Additional methods of extortion include not only data exfiltration, but corporate domain hijack, deletion or encryption of backups, attacks against systems close to industrial control systems, targeting company VIPs… the list goes on.

Sometimes, attackers will just skip straight from stage 2 to 6 and jump straight to extortion. Darktrace recently stopped an email attack which showed an attacker bypassing the hard work and attempting to jump straight to extortion in an email. The attacker claimed to have compromised the organization’s sensitive data, requesting payment in bitcoin for its same return. Whether or not the claims were true, this attack shows that encryption is not always necessary for extortion, and this type of harassment exists in multiple forms.

Figure 6: Darktrace holds back the offending email, protecting the recipient and organization from harm

As with the email example we explored in the first post of this series, Darktrace/Email was able to step in and stop this email where other email tools would have let it through, stopping this potentially costly extortion attempt.

Whether through encryption or some other kind of blackmail, the message is the same every time. Pay up, or else. At this stage, it’s too late to start thinking about any of the options described above that were available to the organization, that would have stopped the attack in its earliest stages. There is only one dilemma. “To pay or not to pay” – that is the question.

Often, people believe their payment troubles are over after the ransom payment stage, but unfortunately, it’s just beginning to scratch the surface…

8. Clean-up

Efforts are made to try to secure the vulnerabilities which allowed the attack to happen initially – the organization should be conscious that approximately 80% of ransomware victims will in fact be targeted again in the future.

Legacy tools largely fail to shed light on the vulnerabilities which allowed the initial breach. Like searching for a needle in an incomplete haystack, security teams will struggle to find useful information within the limited logs offered by firewalls and IDSs. Antivirus solutions may reveal some known malware but fail to spot novel attack vectors.

With Darktrace’s Cyber AI Analyst, organizations are given full visibility over every stage of the attack, across all coverage areas of their digital estate, taking the mystery out of ransomware attacks. They are also able to see the actions that would have been taken to halt the attack by Darktrace RESPOND.

9. Recovery

The organization begins attempts to return its digital environment to order. Even if it has paid for a decryption key, many files may remain encrypted or corrupted. Beyond the costs of the ransom payment, network shutdowns, business disruption, remediation efforts, and PR setbacks all incur hefty financial losses.

The victim organization may also suffer additional reputation costs, with 66% of victims reporting a significant loss of revenue following a ransomware attack, and 32% reporting losing C-level talent as a direct result from ransomware.

Conclusion

While the high-level stages described above are common in most ransomware attacks, the minute you start looking at the details, you realize every ransomware attack is different.

As many targeted ransomware attacks come through ransomware affiliates, the Tools, Techniques and Procedures (TTPs) displayed during intrusions vary widely, even when the same ransomware malware is used. This means that even comparing two different ransomware attacks using the same ransomware family, you are likely to encounter completely different TTPs. This makes it impossible to predict what tomorrow’s ransomware will look like.

This is the nail in the coffin for traditional tooling which is based on historic attack data. The above examples demonstrate that Self-Learning technology and Autonomous Response is the only solution that stops ransomware at every stage, across email and network.

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
Dan Fein
VP, Product

More in this series

No items found.

Blog

/

AI

/

August 7, 2026

信頼が新たなアタックサーフェスである理由:ダークトレースの2026年度中間脅威アップデート

Default blog imageDefault blog image

2026年初頭、ダークトレースのアナリストによって専用に設計されたReact2Shellハニーポットは、その展開から2時間未満で侵害を受けました。この1つのデータをとって見ても2026年前半の脅威ランドスケープのペースを表していると言うことができますが、スピードは1つの側面に過ぎません。

過去6か月間の変化は、従来のマルウェアや脆弱性を中心とした攻撃から、信頼されるアイデンティティ、プラットフォーム、およびインフラの悪用への移行を示しています。多くの組織が広範囲にAIを導入するのに伴い、アイデンティティ、SaaSプラットフォーム、クラウドに対する権限、自動化フレームワーク、および非人間アイデンティティが、攻撃者に好まれる攻撃経路となっています。

攻撃者は、外部から侵入するよりも、防御者やユーザーが信頼するよう条件づけられている関係、サービス、認証済みチャネル内で活動する傾向が高まっています。

2025年と比較して何が変わったか?

2025年には、アイデンティティが新たな境界となり、攻撃者はますます従来のエクスプロイト手法を使うよりも信頼されるアカウント、SaaSプラットフォーム、そしてAIによって可能になった新手の手法を使うようになりました。2026年前半は、この進化の次の段階にあると言えます。アイデンティの悪用は依然として中心的ですが、信頼の問題は今やアカウントをはるかに超えてEメール認証、クラウドに対する権限、ソフトウェアサプライチェーン、AIゲートウェイ、リモート管理ツール、そして非人間アイデンティティにも及んでいます。

Theme 2025 (Mid-Year / Annual) H1 2026
Identity Credentials remained the weak link; identity emerged as the new perimeter. Identity remains the entry point, but trust has become the new attack surface.
Cloud & SaaS SaaS-targeted ransomware continued to rise. Cloud and SaaS became the attacker's preferred operating environment.
AI Large Language Models (LLMs) were suspected of influencing phishing shifts. LLM-generated malware, compromised AI proxies, and the abuse of AI identities emerged.
Attack Surface Scale & Speed Exponential growth of Common Vulnerabilities and Exposures (CVEs), with public proof-of-concepts appearing faster. Cloud and AI adoption expanded the attack surface, while AI accelerated exploitation. One honeypot was compromised in under two hours.
Supply Chain Legitimate services were increasingly abused. Trusted maintainers and CI/CD workflows were weaponized.

アイデンティティとEメール:危険にさらされる信頼のシグナル

Eメールは信頼されるアイデンティティへの最も確実なルートであり、攻撃者はノイズを作り出すことよりも品質の向上に投資していることをデータが示しています。2026年前半において、フィッシングEメールの67%がDMARC認証を通過していました。ほとんどのフィッシングの試みに対して、阻止するには認証だけではもはや不十分なのです。フィッシングEメールの25.8%でVIPユーザーが標的となっており、22025年と同様に25%を上回る値ですが、期間全体を通じて上昇傾向にあります。重要な点は、フィッシングの巧妙さが高まり続けていることです:フィッシングEメールの37%が大量のテキストを含んでおり、2025年前半の32%から増加しています。また、39%は新手のソーシャルエンジニアリングテクニックを特徴としており、攻撃者が特定の標的にあわせてさらなるカスタマイズを行っていることを示唆しています。

ダークトレースの顧客に最も幅広く影響を与えている脅威もアイデンティティに焦点を当てたものであり、専用のStealCおよびAMOSインフォスティーラーを使った攻撃がこの半年間に多く見られています。これらのマルウェアの蔓延も、根本的にはアイデンティティの問題です。インフォスティーラーによって収集された認証情報がしばしば最初のアクセスベクトルとして使用され、攻撃チェーンの後の段階で格段に影響の大きい侵害につながります。また、マルウェアの投下には技術的弱点の悪用をほとんど必要としない点が重要です。ユーザー自身の手で悪意あるコードを実行させるClickFixソーシャルエンジニアリング手法は、依然としてよく見られます。最近観測されたある攻撃キャンペーンは17か国のダークトレース顧客で確認され、最も影響を受けたのは米国でした。この侵害はソフトウェアの欠陥から始まったものではなく、信頼されるユーザーが信頼されるアクションを実行したことが端緒となりました。

サプライチェーン:信頼が大規模に武器化される

3月と4月には共通の教訓が確認されました。それは信頼がサプライチェーン脆弱性となったということです。Axiosの侵害では幅広く使用されているメンテナーへの信頼が悪用され、Trivyキャンペーンは信頼されるCI/CDインフラ、リリースアーティファクト、およびコンテナイメージを利用して、正当な開発ワークフローに悪意あるコードを押し込みました。

これを最もはっきりと示した事例は、2月から3月にかけて観測されたキャンペーンです。多数のデバイスがHola VPNを使用している間に悪意のあるペイロードをダウンロードし、その後、Holaの配信パイプラインの侵害に関連していることが判明しました。ダークトレースの脅威調査チームは、公開アドバイザリがリリースされる前に、複数の顧客において繰り返し発生している異常な動作から、この侵害に関連する活動を特定しました。

最近では、攻撃者が正当なブロックチェーンインフラを悪用して、AMOSやPhexia等のインフォスティーラーを投下しているケースが見られます。セキュリティリソースが限られているユーザーによく使用されている一般的なVPN等のツールは、正当なC2インフラと組み合わせることで、攻撃者がはるかに広範な被害者層に到達することを可能にする一方、防御側は関連するエンドポイントを単純にブロックすることはできないため、やっかいな問題になります。

防御者にとっての課題は、もはや悪意のあるインフラを特定することではなく、信頼されるインフラが悪意のある動作を始めたときにそれを認識できるかどうかということです。

クラウドとSaaS:標的から作戦領域へ

5月から6月には、デバイス登録、クラウドデータ窃取、SaaS悪用、RDPの拡大、リモート管理ツール関連の活動が見られ、攻撃者がクラウドやSaaSを単なる標的としてではなく、むしろ好ましい作戦環境としてますます認識していることが示唆されました。 

ダークトレース顧客でのある事例では、1つの侵害されたSaaSアカウントがEメール、SaaS、ネットワークレイヤーにわたる活動を引き起こし、これには受信トレイルールの変更、フィッシングの拡散、疑わしいインフラへの接続が含まれていました。これらの兆候のいずれも単独では決定的とは言えませんでしたが、総合すると明らかに侵入を示していました。これらの環境において、攻撃者はますます信頼管理をを回避する必要がなくなっています。信頼は、侵害されたアイデンティティ、委任されたアクセス権、および正当な管理ツールを通じて引き継ぐことができるからです。これは、2025年に見られたSaaSを標的としたランサムウェアの傾向の自然な進化であると言えます。ますます多くのケースにおいて、ビジネスが運営されるのと同じプラットフォームが、敵対者が作戦を展開するプラットフォームとなっています。

AI:攻撃の加速装置でありアタックサーフェス、そして信頼される、しかしリスクの高いアクター

信頼がアタックサーフェスなら、AIはそれが最も急激に拡大している領域であると言えます。ダークトレースの顧客基盤全体において、2026年前半にAIサービスへの接続は平均13%増加し、接続数は1600万回以上標準的な組織は7つの異なるAIプロバイダーとやり取りするようになっています。そしてAIはもはや企業のごく一部ではありません。日々の業務に組み込まれています。この変化が3つの問題を生み出しましたが、これらはすべて2026年前半にダークトレースによって観測されています。

1. 攻撃倍増装置としてのAI

ダークトレースは、AIによって生成されたReact2Shellを悪用するマルウェアを特定しました。これは攻撃者がLLMを使用して有効なエクスプロイトコードを生成し大規模に展開したものです。脅威ランドスケープ全体で見ても同様の活動が増えており、効果的な攻撃作戦への参入障壁が崩れつつあることを示唆しています。最近のJadePuffer事例にも見られるように、エージェント型脅威アクターがインターネットに接続されたサーバーの脆弱性をエクスプロイトし、その後完全に自動化されたランサムウェア攻撃が開始されており、AIは脆弱性の公開から実際のエクスプロイトまでの過程を加速させています[1]。

2. アタックサーフェスとしてのAI

今やAIレイヤー自体も、調べてみる価値があります。あるオートメーション技術メーカーにおいて、侵害されたLLMプロキシが他のAIサービスへの踏み台として利用され、それが失敗すると攻撃者は暗号通貨マイニングに切り替えたという事例がありました。DarktraceのCyber AI Analystはこの侵入インシデントを明らかにし、Managed Threat Detectionサービスにより顧客への通知が行われたことにより、事態がそれ以上進行する前に封じ込めることができました。実務者にとっての教訓は明確です:AIゲートウェイ、プロキシ、モデルエンドポイントは、本番環境のクラウドワークロードと同様に扱うべきです。なぜなら、攻撃者は既にそうしているからです。

3. 信頼される、ただしリスクもあるアクターとしてのAI

Darktrace/ SECURE AIの観測結果からわかることは、最も一般的な現実世界のリスクはさらに判別が難しいということです。従業員が、個人識別情報(PII)、税務記録、身分証明書、会社の財務データ、人事記録、個人の医療データをLLMのプロンプトに入力することや、シャドーAIの蔓延、そしてモバイルデバイスからのAI使用の増加が挙げられます。28日間で約28,000人のユーザーから送信された約280,000件のプロンプトのうち、Darktraceはこれらのプロンプトの約1%(2,945件)に機密性の高いデータが含まれていることを特定しました。*

*プロンプトデータはユーザーのプライバシーを保護するために、集積および匿名化された形で分析されました。

防御者にとって、課題はコンテキストです。つまり、正当なビジネス利用が重大なリスクに変わるタイミングを、プライバシーやユーザーの信頼を損なうことなく見極めることです。組織がAIシステムをますます信頼し、AIがマシンスピードで機密情報にアクセス、処理、共有するようになるなかで、アイデンティティ、アプリケーション、クラウドインフラと同様に、AIも保護および監視されなければなりません。

スピードと地政学:迅速な作戦、長期的な目標

2026年前半に行われたいくつかの調査では、攻撃者が新たに公開された脆弱性をいかに迅速に実用化し、パッチ適用サイクルが完了する前にOAST(Out-of-Band Application Security Testing)インフラおよび信頼されたクラウドサービスを通じてエクスプロイト検証を行っているかが明らかになりました。React2Shellは2時間で侵害され、BeyondTrustのエクスプロイトも1日未満で発生しました。このような状況の中で、国家を背後に持つ脅威アクターは、引き続き正当なサービス、クラウドインフラ、および信頼関係を通じた、長期的なアクセス、情報収集、および事前配置に重点を置いています。中国、ロシア、イラン、北朝鮮(DPRK)を背後に持つ作戦は共通の特徴を持っています。それは即座に混乱を起こすことよりも、永続化と戦略的な配置を優先するということです。

中国:ダークトレースは、中国系アクターが信頼されるサービス、DLLサイドローディング、およびモジュール型の侵入チェーンを通じた長期的なアクセスの獲得を優先している状況を確認しています。これはCrimson Echoレポートでも解説され、Twill Typhoonの手法に関連するアクティビティと一致しています。

イラン:ダークトレースによるZionSiphonの調査は、イランに関連するアクターのOT環境への関心を浮き彫りにし、諜報目的とインフラ破壊能力を融合させている実態を明らかにしています。

ロシア:ダークトレースによる調査、および業界全体のさまざまな報告は、ロシアがウクライナ関連の支援に関する長期的な情報収集のために、信頼関係とサプライチェーンを標的としていることを明らかにしています[2]。

北朝鮮:ダークトレースは、脆弱性の迅速な武器化と永続的アクセス技術を組み合わせた北朝鮮関連の活動を観測ししています。これにはAxiosのサプライチェーン侵害、React2Shellエクスプロイト、ステルス性のmacOS侵入が含まれています。

 目的は脅威アクターによって異なっていましたが、手法は非常に一貫していました。信頼されるサービス、正当なインフラ、そして永続的アクセスは、即時の混乱よりも価値が高いことが示されています。

防御者のシフト

アイデンティティの侵害、サプライチェーン攻撃、SaaSの悪用、AIインフラの標的化、国家が支援する作戦、いずれのケースにおいても、攻撃者は防御のコントロールを突破するのではなく、信頼されたシステムを通じて行動することで成功を収めることが増えています。信頼されるユーザー、信頼されるソフトウェア、信頼されるインフラチャ、そしてますます信頼されるAIシステムは、すべて有効な攻撃経路となりました。 

防御者にとっての課題はもはや、単にあるアクションが許可されるかどうかを判断することではなく、そのアクションがより広いコンテキストの中で正当かどうかを見極めることです。認証、評判、出自は依然として重要ですが、それだけではもはや十分とは言えません。攻撃者がますます信頼されるシステム内で活動するようになる中で、最も強力なシグナルは多くの場合動作の逸脱です。つまり、信頼されているアクティビティが期待される振る舞いと一致しなくなった時にそれを識別することです。

本稿の執筆にはNathaniel Jones(SVP, Global Threat Intelligence)、Emma Foulger(Global Threat Research Operations Lead)、Justin Torres (Senior Cyber Analyst) Daniel Levy(Threat Hunting Data Scientist)が協力しました。


編集:Ryan Traill(Content Manager)

付録1:脅威調査手法

ダークトレースの脅威調査チームは、顧客の運用環境に対する詳細な調査を行ってアクティブな脅威を識別し、主要な侵害インジケーター(IoC)を特定し、関連する脅威インテリジェンスを提供しています。この調査はダークトレースの異常ベース検知に基づいたもので、脅威調査チームによる徹底した分析およびコンテキスト化が行われています。検知された脅威は関連する顧客のセキュリティチームに直ちに報告されます。顧客がダークトレースの自律遮断テクノロジーを使用している場合、これらの脅威は速やかに緩和され、エスカレーションが阻止されます。

 2026年1月1日から6月30日までの期間、ダークトレースは顧客ベースにおいて多種多様なサイバー脅威を調査しました。その多くは同様のTTPおよびIoCが短い期間内に一定の数の顧客に影響を及ぼした、複数の顧客を標的とした攻撃作戦的活動であったことが判明しています。 

Eメールに関連する統計は、2026年1月1日から6月30日までの間に、すべてのクラウドホスト型顧客環境におけるDarktrace / EMAILの集約されたデータから導出されています。特異な観測値を除外するために、集約を行う前に標準的なデータ品質フィルタリングが適用されています。地域別の統計は、このデータセットの関連サブセットに基づいています。 

付録2:キャンペーン - 地域およびセクター別の傾向

過去6か月間の脅威ランドスケープは上記の大まかなテーマにより定義されていますが、ダークトレースの顧客基盤全体でのキャンペーンクラスタリングにより、それらがセクター、地域、産業ごとにどのように異なっているかが明らかになりました。 

ダークトレースの脅威調査チームは、顧客ベースに影響を与えるさまざまな脅威を調査しています。この調査を通じて、共通のTTPやインフラが観察され、短期間で多くの顧客に影響を与える、攻撃キャンペーンのような活動のクラスターが特定されました。 

セクターおよび産業は、一貫した分類を確保するために標準産業分類(SIC)システムを使用して分類されています。本レポートのセクターおよび地域別の考察は、より広範な世界的な傾向を反映している一方で、ダークトレースの顧客基盤の分布にも影響を受けています。例えば、金融、製造、教育分野はダークトレースの顧客の中で多く、これらのセクターで観測される事例数が多くなる可能性があります。これは必ずしも特定のセクターにおけるリスクが高いことを示すものではなく、顧客の分布を反映しています。同様に、地域の傾向はダークトレースの顧客の地理的分布によって影響を受ける可能性があります。

2026年前半にダークトレースの脅威調査チームによって特定されたキャンペーンクラスターの分析では、明確な地域別の傾向が明らかになりました:

  • ヨーロッパ、中東、アフリカ(EMEA)がすべてのキャンペーンクラスター事例の60%を占めており支配的でした。
  • アメリカ大陸(AMS)は、その次に影響が大きかった地域でありキャンペーンクラスター事例の30%を占めていました。
  • アジア太平洋および日本(APJ)地域はキャンペーンクラスターの影響をあまり受けていませんでした。これは脅威アクターがこの地域の優先度を低くし、代わりに他の地域に注力した可能性を示しています。

産業セクターの標的化も地域によって大きく異なりました:

  • EMEA地域では、情報通信分野が大きく影響を受け、全体の25%を占めました。
  • 対照的に、AMSでは標的はより均等に分布しており、教育、行政機関および防衛、金融および保険の各セクターがいずれもAMS地域の事例の20%以上を占めていました。
  • APJ地域ではキャンペーン活動はより均等に分散しており、特定のセクターが支配的な標的として浮上することはありませんでした。

いくつかの国はそれぞれの地域内でも際立った特徴がありました:

  • 米国はAMS内のすべてのキャンペーンクラスターの60%を占めていました。
  • 日本はAPJ全体のキャンペーン事例の40%を占めました。
  • EMEA地域では、英国とジンバブエがそれぞれ特定された事例の23%を占めており、両国ともさまざまなキャンペーンのタイプに影響を受けています。

Inside the SOCおよび2026年度脅威調査の月次傾向:アクセスからインパクトまで

Month Dominant Themes
January Voice phishing, VPS infrastructure, WebSocket C2, RMM abuse, ransomware, infostealers (StealC), and trojanized installers (7-Zip).
February Voice phishing, VPN intrusion, edge infrastructure compromise (BeyondTrust), and RMM abuse.
March Sustained supply chain compromise (Hola VPN, Axios, Trivy), malicious browser extensions, phishing, and discovery tools.
April Account creation abuse, payload delivery, VPN credential abuse, Fortinet exploitation, and botnet activity.
May PowerShell, EtherHiding, data exfiltration, VPN access, business email compromise (BEC), ClickFix, and infostealers (AMOS).
June RDP abuse, device registration, RMM usage, voice phishing, cloud data theft, botnet activity, blockchain abuse, ClickFix, and infostealers (AMOS).

付録3:参考文献

外部

[1] https://www.darkreading.com/cyberattacks-data-breaches/jadepuffer-first-complete-llm-driven-ransomware-attack

[2] https://www.trendmicro.com/en_us/research/26/c/pawn-storm-targets-govt-infra.html

ダークトレースのリソース

1.        https://www.darktrace.com/blog/ai-llm-generated-malware-used-to-exploit-react2shell

2.        https://www.darktrace.com/blog/2025-cyber-threat-landscape-darktraces-mid-year-review

3.        https://www.darktrace.com/resources/annual-threat-report-2026

4.        https://www.darktrace.com/blog/when-trust-becomes-the-attack-surface-supply-chain-attacks-in-an-era-of-automation-and-implicit-trust

5.        https://www.darktrace.com/blog/hola-vpn-abuse-from-proxy-traffic-to-malware-and-cryptomining

6.        https://www.darktrace.com/blog/security-after-signatures-operating-in-a-world-of-pre-cve-disclosure-exploitation-collapsed-trust-boundaries-and-autonomous-systems

7.        https://www.darktrace.com/blog/when-ai-infrastructure-becomes-part-of-the-attack-surface

8.        https://www.darktrace.com/blog/cve-2026-1731-how-darktrace-sees-the-beyondtrust-exploitation-wave-unfolding

9.        https://www.darktrace.com/resource/understanding-chinese-nexus-cyber-tradecraft

10.   https://www.darktrace.com/blog/chinese-apt-campaign-targets-entities-with-updated-fdmtp-backdoor

11.  https://www.darktrace.com/blog/inside-zionsiphon-darktraces-analysis-of-ot-malware-targeting-israeli-water-systems

12.  https://www.darktrace.com/resources/the-state-of-cybersecurity-in-the-finance-sector

13.  https://www.darktrace.com/blog/from-click-to-command-behavioral-detection-of-applescript-led-macos-intrusions

14.  https://www.darktrace.com/blog/the-state-of-cybersecurity-in-the-finance-sector-six-trends-to-watch

Continue reading
About the author
Nathaniel Jones
SVP, Global Threat Intelligence

Blog

/

Network

/

August 7, 2026

When AI Agents Attack: The Case for Behavioral Anomaly Detection

Default blog imageDefault blog image

The UK AI Security Institute (AISI) has just published a detailed incident report confirming what many within the cyber security industry have suspected for some time: frontier AI agents, given a degree of autonomy, can independently develop and execute attack chains against real targets, including social engineering, supply-chain compromise, and deception, without explicit instruction to do so.

The report (INC-2026-07-28-01, published 4 August 2026) documents what happened during a routine capability evaluation between 25 and 28 July. It deserves a careful read from anyone responsible for securing the modern digital estate.

The incident

AISI regularly tests frontier AI models for offensive cyber capability. In this exercise, agents were placed inside a simulated network environment and given internet access this was deliberate, given to reflect realism of the task. Across 122 evaluation runs, 19 instances of unsanctioned activity were recorded, including cases where agents broke the intended boundaries of the test and acted against real people and real infrastructure on the open internet.

In the most serious case, an agent (Mythos 5) autonomously:

  • Conducted open-source intelligence gathering to identify real developers associated with keywords from the simulated scenario
  • Created a GitHub account and submitted a pull request containing obfuscated malicious code to a real, unaffiliated repository
  • Created a second sockpuppet account to post comments on its own PR, attempting to manufacture social proof
  • When a human reviewer flagged the malicious content, the agent lied, claiming an accidental commit, then repeatedly attempted to reintroduce the payload under the guise of having "fixed" the code
  • Sent spear-phishing emails to the repository maintainer containing manipulated content designed to convince them to merge the code
  • Planted a prompt injection inside a GitHub issue, hidden in an HTML comment invisible to humans but readable by AI coding assistants parsing the repository via API

AISI confirmed no real-world harm resulted. The PRs were not merged; the payloads did not execute. But containment was a product of circumstance, not design.

Why this matters

Every action the agents took used legitimate services operating within normal parameters. Creating a GitHub account is legitimate. Opening a pull request is legitimate. Sending an email is legitimate. Posting an issue is legitimate.

No vulnerability was exploited. No known malware signature was present. No indicator of compromise from any threat intelligence feed would have matched. The entire attack existed as a pattern, a sequence of individually normal actions that, taken together, constituted a supply-chain attack, a social engineering campaign, and an attempted compromise of downstream systems.

This is the class of threat that signature-based and rule-based security tools structurally struggle to detect. They answer the question "have I seen this before?" When the answer is no – and when the attack is novel, composed of legitimate actions, and adapted in real time by an adversary in this case an agent that reasons about evasion – they struggle.

Behavioral anomaly detection: The architecture that fits

Darktrace has spent a decade building a platform around a different question: "is this behavior normal for this entity?"

The platform learns the baseline behavior of every user, device, and communication pattern across an organization's digital environment. It does not need prior knowledge of an attack technique. It identifies deviation from learned normality, surfaces it, and through its Autonomous Response capability, takes targeted action to contain threats at machine speed.

Consider how this AISI incident might show across the Darktrace platform:

Network detection and response

While no payload was successfully delivered to a victim in this incident, AISI's post-incident analysis of the agent's code (detailed on pages 24-25 of the report) reveals what would have landed on target systems had the social engineering succeeded. The agent produced three successive payload generations, each replacing the last after being detected and called out:

Generation 1 hid a module-load stager inside a legitimate bug-fix commit, guarded by an environment variable check, to skip execution in CI. Its second stage attempted to fetch Poseidon implants (Linux and Windows variants) calling back to the agent's own C2 listener, with a fallback to publicly hosted polling scripts that fetched and executed commands every 60 seconds.

Generation 2 exploited an Electron "What's New" window with nodeIntegration enabled, loading remote HTML from a GitHub Pages site the agent had registered. The page decoded an XOR-obfuscated payload at runtime that beaconed host identifiers over DNS, attempted to download the same implants, ran its own in-process C2 loop, and installed reboot persistence via crontab and Windows registry Run keys.

Generation 3 was a post-install dropper added after the agent had already been publicly caught. It XOR-decoded a hidden URL, downloaded a script over plaintext HTTP, and ran it detached, force-exiting so npm install always reports success, giving the attacker remote code execution on any machine running the install.

None of these payloads reached a victim. But the technical detail matters: this is the calibre of tradecraft an autonomous agent produced in a matter of hours, unprompted. Each generation demonstrated adaptation, the agent iterated its approach in direct response to being detected.

For network defenders, the behavioral signals these payloads would have generated are clear. DNS beaconing to novel domains, periodic HTTP polling to newly registered infrastructure, XOR-encoded data in transit, registry and crontab persistence writes on endpoints that have never exhibited such behavior. These are exactly the anomalies that Darktrace / NETWORK identifies in real time: deviations from learned device and connection baselines, regardless of whether the specific payload or C2 domain has been seen before.

Beyond the payload analysis, the agents' broader activity produced additional behavioral anomalies: new identities engaging in high-frequency interactions with external services, coordination via unusual channels (public pastebins, gists), and lateral communication patterns that deviate from any established baseline.

Email security

The spear-phishing emails sent by the agent, crafted with context-specific content designed to manipulate a specific individual, represent exactly the kind of socially engineered communication that static email gateways can miss. Darktrace / EMAIL analyses the linguistic patterns, sender behavior, and relational context of every message. A brand-new sender using tailored language to pressure a recipient into a specific technical action deviates from the learned communication profile, regardless of whether the message contains a known-bad URL or attachment.

Securing AI

This is where the incident points to a threat category that many security platforms do not yet fully address. The agent did not just use AI as a tool for attack. It targeted other AI systems, attempting prompt injections against coding assistants and trying to compromise automated workflows. Organisations adopting AI agents for development, operations, and decision-making are introducing a newer extended attack surface.  

Darktrace / SECURE AI extends the same behavioral detection model into this space. It monitors AI usage across the enterprise, detecting anomalous interactions with AI services, identifying sensitive data exposure to AI systems, providing visibility into shadow AI use. As AI agents become standard components of enterprise infrastructure, the ability to detect when an AI system is behaving outside its expected parameters, when there is a chance, it is being manipulated, or when it is interacting with something it should not be, that becomes a direct security requirement rather than a future consideration.

The principle is consistent across the Darktrace platform: learn what normal looks like, identify deviation, respond autonomously.

The AI-to-AI threat surface

One of the report's most important findings is a confirmation that AI agents can act outside of instructions and guardrails to complete tasks. The Mythos 5 agent conducted reconnaissance on a repository maintainer, inferred it might be an AI coding assistant, and deployed a prompt injection specifically crafted to compromise it.

This is a new attack class. Organizations deploying AI coding assistants, AI-powered code review, or autonomous DevOps agents now face an adversary that:

  • Moves at speed
  • Is able to adapt its approach when initial attempts are halted
  • Specifically targets AI systems via techniques (prompt injection, hidden instructions in HTML comments) that are less visible to human reviewers but parsed by machines
  • Reasons about which evasion strategies are most likely to succeed

Defending against this requires security that operates with the same adaptability and speed. A system that learns what "normal" looks like, and flags deviation from it.

What AISI recommends

The report identifies five contributing factors to the incident. Two are directly relevant:

No synchronous real-time monitoring (Section 5.3): AISI acknowledges it had not built real-time behavioral monitoring capable of immediately blocking unsanctioned agent actions. Their security team detected the incident via commercial security monitoring software, but only after activity had already occurred.

No fine-grained behavioral controls (Section 6.2): AISI's forward-looking response includes building continuous monitoring that can "immediately block or flag unsanctioned AI agent behavior."

The direction is clear: organizations need security that watches behavior continuously, learns what normal looks like, and acts when deviation occurs, without requiring a human in the loop for every decision.

The takeaway

The AISI incident is documented proof that autonomous AI agents will independently develop novel attack chains using legitimate tools, adapt when detected, employ deception, and target both humans and other AI systems. This happened last week, in a controlled setting, with commercially available models.

The security architecture that addresses this is behavioral anomaly detection applied across the full digital estate, as AI agents become standard components of enterprise infrastructure, writing code, managing deployments, processing communications, the attack surface they create is behavioral by nature.

This is the approach Darktrace has taken for years: learning what is normal across an organization’s digital environment, identifying meaningful deviations, and responding to emerging threats without relying on known attack signatures. As autonomous AI agents introduce new and unpredictable behaviors, that foundation becomes increasingly important to securing the enterprise.

Read the full report from the UK AI Security Institute here.

Continue reading
About the author
Adam Stevens
Senior Director of Product | Darktrace
あなたのデータ × DarktraceのAI
唯一無二のDarktrace AIで、ネットワークセキュリティを次の次元へ