ブログ
/
Network
/
February 29, 2024

Protecting Against AlphV BlackCat Ransomware

Learn how Darktrace AI is combating AlphV BlackCat ransomware, including the details of this ransomware and how to protect yourself from it.
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
Sam Lister
Specialist Security Researcher
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
29
Feb 2024

As-a-Service malware trending

Throughout the course of 2023, “as-a-Service” strains of malware remained the most consistently observed threat type to affect Darktrace customers, mirroring their overall prominence across the cyber threat landscape. With this trend expected to continue throughout 2024, organizations and their security teams should be prepared to defend their network against increasingly versatile and tailorable malware-as-a-service (MaaS) and ransomware-as-a-service (RaaS) strains [1].

What is ALPHV ransomware?

The ALPHV ransomware, also known as ‘BlackCat’ or ‘Noberus’, is one example of a RaaS strain that has been prominent across the threat landscape over the last few years.

ALPHV is a ransomware strain coded in the Rust programming language. The ransomware is sold as part of the RaaS economy [2], with samples of the ransomware being provided and sold by a criminal group (the RaaS ‘operator’) to other cybercriminals (the RaaS ‘affiliates’) who then gain entry to organizations' networks with the intention of detonating the ransomware and demanding ransom payments.

ALPHV was likely first used in the wild back in November 2021 [3]. Since then, it has become one of the most prolific ransomware strains, with the Federal Bureau of Investigation (FBI) reporting nearly USD 300 million in ALPHV ransom payments as of September 2023 [4].

In December 2023, the FBI and the US Department of Justice announced a successful disruption campaign against the ALPHV group, which included a takedown of the their data leak site, and the release of a decryption tool for the ransomware strain [5], and in February 2024, the US Department of State announced  a reward of up to USD 10 million for information leading to the identification or location of anyone occupying a key leadership position in the group operating the ALPHV ransomware strain [6].

The disruption campaign against the ransomware group appeared to have been successful, as evidenced by the recent, significant decline in ALPHV attacks, however, it would not be surprising for the group to simply return with new branding, in a similar vein to its apparent predecessors, DarkSide and BlackMatter [7].

How does ALPHV ransomware work?

ALPHV affiliates have been known to employ a variety of methods to progress towards their objective of detonating ALPHV ransomware [4]. In the latter half of 2023, ALPHV affiliates were observed using malicious advertising (i.e, malvertising) to deliver a Python-based backdoor-dropper known as 'Nitrogen' to users' devices [8][12]. These malvertising operations consisted in affiliates setting up malicious search engine adverts for tools such as WinSCP and AnyDesk.

Users' interactions with these adverts led them to sites resembling legitimate software distribution sites. Users' attempts to download software from these spoofed sites resulted in the delivery of a backdoor-dropping malware sample dubbed 'Nitrogen' to their devices. Nitrogen has been observed dropping a variety of command-and-control (C2) implants onto users' devices, including Cobalt Strike Beacon and Sliver C2. ALPHV affiliates often used the backdoor access afforded to them by these C2 implants to conduct reconnaissance and move laterally, in preparation for detonating ALPHV ransomware payloads.

Darktrace Detection of ALPHV Ransomware

During October 2023, Darktrace observed several cases of ALPHV affiliates attempting to infiltrate organizations' networks via the use of malvertising to socially engineer users into downloading and installing Nitrogen from impersonation websites such as 'wireshhark[.]com' and wìnscp[.]net (i.e, xn--wnscp-tsa[.]net).

While the attackers managed to bypass traditional security measures and evade detection by using a device from the customer’s IT team to perform its malicious activity, Darktrace DETECT™ swiftly identified the subtle indicators of compromise (IoCs) in the first instance. This swift detection of ALPHV, along with Cyber AI Analyst™ autonomously investigating the wide array of post-compromise activity, provided the customer with full visibility over the attack enabling them to promptly initiate their remediation and recovery efforts.

Unfortunately, in this incident, Darktrace RESPOND™ was not fully deployed within their environment, hindering its ability to autonomously counter emerging threats. Had RESPOND been fully operational here, it would have effectively contained the attack in its early stages, avoiding the eventual detonation of the ALPHV ransomware.

Figure 1: Timeline of the ALPHV ransomware attack.

In mid-October, a member of the IT team at a US-based Darktrace customer attempted to install the network traffic analysis software, Wireshark, onto their desktop. Due to the customer’s configuration, Darktrace's visibility over this device was limited to its internal traffic, despite this it was still able to identify and alert for a string of suspicious activity conducted by the device.

Initially, Darktrace observed the device making type A DNS requests for 'wiki.wireshark[.]org' immediately before making type A DNS requests for the domain names 'www.googleadservices[.]com', 'allpcsoftware[.]com', and 'wireshhark[.]com' (note the two 'h's). This pattern of activity indicates that the device’s user was redirected to the website, wireshhark[.]com, as a result of the user's interaction with a sponsored Google Search result pointing to allpcsoftware[.]com.

At the time of analysis, navigating to wireshhark[.]com directly from the browser search bar led to a YouTube video of Rick Astley's song "Never Gonna Give You Up". This suggests that the website, wireshhark[.]com, had been configured to redirect users to this video unless they had arrived at the website via the relevant sponsored Google Search result [8].

Although it was not possible to confirm this with certainty, it is highly likely that users who visited the website via the appropriate sponsored Google Search result were led to a fake website (wireshhark[.]com) posing as the legitimate website, wireshark[.]com. It seems that the actors who set up this fake version of wireshark[.]com were inspired by the well-known bait-and-switch technique known as 'rickrolling', where users are presented with a desirable lure (typically a hyperlink of some kind) which unexpectedly leads them to a music video of Rick Astley's "Never Gonna Give You Up".

After being redirected to wireshhark[.]com, the user unintentionally installed a malware sample which dropped what appears to be Cobalt Strike onto their device. The presence of Cobalt Strike on the user's desktop was evidenced by the subsequent type A DNS requests which the device made for the domain name 'pse[.]ac'. These DNS requests were responded to with the likely Cobalt Strike C2 server address, 194.169.175[.]132. Given that Darktrace only had visibility over the device’s internal traffic, it did not observe any C2 connections to this Cobalt Strike endpoint. However, the desktop's subsequent behavior suggests that a malicious actor had gained 'hands-on-keyboard' control of the device via an established C2 channel.

Figure 2: Advanced Search data showing an customer device being tricked into visiting the fake website, wireshhark[.]com.

Since the malicious actor had gained control of an IT member's device, they were able to abuse the privileged account credentials to spread Python payloads across the network via SMB and the Windows Management Instrumentation (WMI) service. The actor was also seen distributing the Windows Sys-Internals tool, PsExec, likely in an attempt to facilitate their lateral movement efforts. It was normal for this IT member's desktop to distribute files across the network via SMB, which meant that this malicious SMB activity was not, at first glance, out of place.

Figure 3: Advanced Search data showing that it was normal for the IT member's device to distribute files over SMB.

However, Darktrace DETECT recognized that the significant spike in file writes being performed here was suspicious, even though, on the surface, it seemed ‘normal’ for the device. Furthermore, Darktrace identified that the executable files being distributed were attempting to masquerade as a different file type, potentially in an attempt to evade the detection of traditional security tools.

Figure 4: Event Log data showing several Model Breaches being created in response to the IT member's DEVICE's SMB writes of Python-based executables.

An addition to DETECT’s identification of this unusual activity, Darktrace’s Cyber AI Analyst launched an autonomous investigation into the ongoing compromise and was able to link the SMB writes and the sharing of the executable Python payloads, viewing the connections as one lateral movement incident rather than a string of isolated events. After completing its investigation, Cyber AI Analyst was able to provide a detailed summary of events on one pane of glass, ensuring the customer could identify the affected device and begin their remediation.

Figure 5: Cyber AI Analyst investigation summary highlighting the IT member's desktop’s lateral movement activities.

C2 Activity

The Python payloads distributed by the IT member’s device were likely related to the Nitrogen malware, as evidenced by the payloads’ names and by the network behaviours which they engendered.  

Figure 6: Advanced Search data showing the affected device reaching out to the C2 endpoint, pse[.]ac, and then distributing Python-based executable files to an internal domain controller.

The internal devices to which these Nitrogen payloads were distributed immediately went on to contact C2 infrastructure associated with Cobalt Strike. These C2 connections were made over SSL on ports 443 and 8443.  Darktrace identified the attacker moving laterally to an internal SQL server and an internal domain controller.

Figure 7: Advanced Search data showing an internal SQL server contacting the Cobalt Strike C2 endpoint, 194.180.48[.]169, after receiving Python payloads from the IT member’s device.
Figure 8: Event Log data showing several DETECT model breaches triggering in response to an internal SQL server’s C2 connections to 194.180.48[.]169.

Once more, Cyber AI Analyst launched its own investigation into this activity and was able to successfully identify a series of separate SSL connections, linking them together into one wider C2 incident.

Figure 9: Cyber AI Analyst investigation summary highlighting C2 connections from the SQL server.

Darktrace observed the attacker using their 'hands-on-keyboard' access to these systems to elevate their privileges, conduct network reconnaissance (primarily port scanning), spread Python payloads further across the network, exfiltrate data from the domain controller and transfer a payload from GitHub to the domain controller.

Figure 10: Cyber AI Analyst investigation summary an IP address scan carried out by an internal domain controller.
Figure 12: Event Log data showing an internal domain controller contacting GitHub around the time that it was in communication with the C2 endpoint, 194.180.48[.]169.
Figure 13: Event Log data showing a DETECT model breach being created in response to an internal domain controller's large data upload to the C2 endpoint, 194.180.48[.]169.

After conducting extensive reconnaissance and lateral movement activities, the attacker was observed detonating ransomware with the organization's VMware environment, resulting in the successful encryption of the customer’s VMware vCenter server and VMware virtual machines. In this case, the attacker took around 24 hours to progress from initial access to ransomware detonation.  

If the targeted organization had been signed up for Darktrace's Proactive Threat Notification (PTN) service, they would have been promptly notified of these suspicious activities by the Darktrace Security Operations Center (SOC) in the first instance, allowing them to quickly identify affected devices and quarantine them before the compromise could escalate.

Additionally, given the quantity of high-severe alerts that triggered in response to this attack, Darktrace RESPOND would, under normal circumstances, have inhibited the attacker's activities as soon as they were identified by DETECT. However, due to RESPOND not being configured to act on server devices within the customer’s network, the attacker was able to seamlessly move laterally through the organization's server environment and eventually detonate the ALPHV ransomware.

Nevertheless, Darktrace was able to successfully weave together multiple Cyber AI Analyst incidents which it generated into a thread representing the chain of behavior that made up this attack. The thread of Incident Events created by Cyber AI Analyst provided a substantial account of the attack and the steps involved in it, which significantly facilitated the customer’s post-incident investigation efforts.  

Figure 14: Darktrace's AI Analyst weaved together 33 of the Incident Events it created together into a thread representing the attacker’s chain of behavior.

Conclusion

It is expected for malicious cyber actors to revise and upgrade their methods to evade organizations’ improving security measures. The continued improvement of email security tools, for example, has likely created a need for attackers to develop new means of Initial Access, such as the use of Microsoft Teams-based malware delivery.

This fast-paced ALPHV ransomware attack serves as a further illustration of this trend, with the actor behind the attack using malvertising to convince an unsuspecting user to download the Python-based malware, Nitrogen, from a fake Wireshark site. Unbeknownst to the user, this stealthy malware dropped a C2 implant onto the user’s device, giving the malicious actor the ‘hands-on-keyboard’ access they needed to move laterally, conduct network reconnaissance, and ultimately detonate ALPHV ransomware.

Despite the non-traditional initial access methods used by this ransomware actor, Darktrace DETECT was still able to identify the unusual patterns of network traffic caused by the attacker’s post-compromise activities. The large volume of alerts created by Darktrace DETECT were autonomously investigated by Darktrace’s Cyber AI Analyst, which was able to weave together related activities of different devices into a comprehensive timeline of the attacker’s operation. Given the volume of DETECT alerts created in response to this ALPHV attack, it is expected that Darktrace RESPOND would have autonomously inhibited the attacker’s operation had the capability been appropriately configured.

As the first post-compromise activities Darktrace observed in this ALPHV attack were seemingly performed by a member of the customer’s IT team, it may have looked normal to a human or traditional signature and rules-based security tools. To Darktrace’s Self-Learning AI, however, the observed activities represented subtle deviations from the device’s normal pattern of life. This attack, and Darktrace’s detection of it, is therefore a prime illustration of the value that Self-Learning AI can bring to the task of detecting anomalies within organizations’ digital estates.

Credit to Sam Lister, Senior Cyber Analyst, Emma Foulger, Principal Cyber Analyst

Appendices

Darktrace DETECT Model Breaches

- Compliance / SMB Drive Write

- Compliance / High Priority Compliance Model Breach

- Anomalous File / Internal / Masqueraded Executable SMB Write

- Device / New or Uncommon WMI Activity

- Anomalous Connection / New or Uncommon Service Control

- Anomalous Connection / High Volume of New or Uncommon Service Control

- Device / New or Uncommon SMB Named Pipe

- Device / Multiple Lateral Movement Model Breaches

- Device / Large Number of Model Breaches  

- SMB Writes of Suspicious Files (Cyber AI Analyst)

- Suspicious Remote WMI Activity (Cyber AI Analyst)

- Suspicious DCE-RPC Activity (Cyber AI Analyst)

- Compromise / Connection to Suspicious SSL Server

- Compromise / High Volume of Connections with Beacon Score

- Anomalous Connection / Suspicious Self-Signed SSL

- Anomalous Connection / Anomalous SSL without SNI to New External

- Compromise / Suspicious TLS Beaconing To Rare External

- Compromise / Beacon to Young Endpoint

- Compromise / SSL or HTTP Beacon

- Compromise / Agent Beacon to New Endpoint

- Device / Long Agent Connection to New Endpoint

- Compromise / SSL Beaconing to Rare Destination

- Compromise / Large Number of Suspicious Successful Connections

- Compromise / Slow Beaconing Activity To External Rare

- Anomalous Server Activity / Outgoing from Server

- Device / Multiple C2 Model Breaches

- Possible SSL Command and Control (Cyber AI Analyst)

- Unusual Repeated Connections (Cyber AI Analyst)

- Device / ICMP Address Scan

- Device / RDP Scan

- Device / Network Scan

- Device / Suspicious Network Scan Activity

- Scanning of Multiple Devices (Cyber AI Analyst)

- ICMP Address Scan (Cyber AI Analyst)

- Device / Anomalous Github Download

- Unusual Activity / Unusual External Data Transfer

- Device / Initial Breach Chain Compromise

MITRE ATT&CK Mapping

Resource Development techniques:

- Acquire Infrastructure: Malvertising (T1583.008)

Initial Access techniques:

- Drive-by Compromise (T1189)

Execution techniques:

- User Execution: Malicious File (T1204.002)

- System Services: Service Execution (T1569.002)

- Windows Management Instrumentation (T1047)

Defence Evasion techniques:

- Masquerading: Match Legitimate Name or Location (T1036.005)

Discovery techniques:

- Remote System Discovery (T1018)

- Network Service Discovery (T1046)

Lateral Movement techniques:

- Remote Services: SMB/Windows Admin Shares

- Lateral Tool Transfer (T1570)

Command and Control techniques:

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

- Encrypted Channel: Asymmetric Cryptography (T1573.002)

- Non-Standard Port (T1571)

- Ingress Tool Channel (T1105)

Exfiltration techniques:

- Exfiltration Over C2 Channel (T1041)

Impact techniques:

- Data Encrypted for Impact (T1486)

List of Indicators of Compromise

- allpcsoftware[.]com

- wireshhark[.]com

- pse[.]ac • 194.169.175[.]132

- 194.180.48[.]169

- 193.42.33[.]14

- 141.98.6[.]195

References  

[1] https://darktrace.com/threat-report-2023

[2] https://www.microsoft.com/en-us/security/blog/2022/05/09/ransomware-as-a-service-understanding-the-cybercrime-gig-economy-and-how-to-protect-yourself/

[3] https://www.bleepingcomputer.com/news/security/alphv-blackcat-this-years-most-sophisticated-ransomware/

[4] https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-353a

[5] https://www.justice.gov/opa/pr/justice-department-disrupts-prolific-alphvblackcat-ransomware-variant

[6] https://www.state.gov/u-s-department-of-state-announces-reward-offers-for-criminal-associates-of-the-alphv-blackcat-ransomware-variant/

[7] https://www.bleepingcomputer.com/news/security/blackcat-alphv-ransomware-linked-to-blackmatter-darkside-gangs/

[8] https://www.trendmicro.com/en_us/research/23/f/malvertising-used-as-entry-vector-for-blackcat-actors-also-lever.html

[9] https://news.sophos.com/en-us/2023/07/26/into-the-tank-with-nitrogen/

[10] https://www.esentire.com/blog/persistent-connection-established-nitrogen-campaign-leverages-dll-side-loading-technique-for-c2-communication

[11] https://www.esentire.com/blog/nitrogen-campaign-2-0-reloads-with-enhanced-capabilities-leading-to-alphv-blackcat-ransomware

[12] https://www.esentire.com/blog/the-notorious-alphv-blackcat-ransomware-gang-is-attacking-corporations-and-public-entities-using-google-ads-laced-with-malware-warns-esentire

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
Sam Lister
Specialist Security Researcher

More in this series

No items found.

Blog

/

AI

/

May 18, 2026

AI Insider Threats: How Generative AI is Changing Insider Risk

Default blog imageDefault blog image

How generative AI changes insider behavior

AI systems, especially generative platforms such as chatbots, are designed for engagement with humans. They are equipped with extraordinary human-like responses that can both confirm, and inflate, human ideas and ideology; offering an appealing cognitive partnership between machine and human.  When considering this against the threat posed by insiders, the type of diverse engagement offered by AI can greatly increase the speed of an insider event, and can facilitate new attack platforms to carry out insider acts.  

This article offers analysis on how to consider this new paradigm of insider risk, and outlines key governance principles for CISOs, CSOs and SOC managers to manage the threats inherent with AI-powered insider risk.

What is an insider threat?

There are many industry or government definitions of what constitutes insider threat. At its heart, it relates to the harm created when trusted access to sensitive information, assets or personnel is abused bywith malicious intent, or through negligent activities.  

Traditional methodologies to manage insider threat have relied on two main concepts: assurance of individuals with access to sensitive assets, and a layered defense system to monitor for any breach of vulnerability. This is often done both before, and after access has been granted.  In the pre-access state, assurance is gained through security or recruitment checks. Once access is granted, controls such as privileged access, and zero-trust architecture offer defensive layers.

How does AI change the insider threat paradigm?

While these two concepts remain central to the management of insider threats, the introduction of AI offers three key new aspects that will re-shape the paradigm:.  

AI can act as a cognitive amplifier, influencing and affecting the motivations that can lead to insider-related activity. This is especially relevant for the deliberate insider - someone who is considering an act of insider harm. These individuals can now turn to AI systems to validate their thinking, provide unique insights, and, crucially, offer encouragement to act. With generative systems hard-wired to engage and agree with users, this can turn a helpful AI system into a dangerous AI hype machine for those with harmful insider intent.  

AI can act as an operational enabler. AI can now develop and increase the range of tools needed to carry out insider acts. New social engineering platforms such as vishing and deepfakes give adversaries a new edge to create insider harm. AI can generate solutions and operational platforms at increasing speeds; often without the need for human subject matter expertise to execute the activities. As one bar for advanced AI capabilities continues to be raised, the bar needed to make use of those platforms has become significantly lower.

AI can act as a semi-autonomous insider, particularly when agentic AI systems or non-human identities are provided broad levels of autonomy; creating a vector of insider acts with little-to-no human oversight or control. As AI agents assume many of the orchestration layers once reserved for humans, they do so without some of the restricted permissions that generally bind service accounts. With broad levels of accessibility and authority, these non-human identities (NHIs) can themselves become targets of insider intent.  Commonly, this refers to the increasing risks of prompt injection, poisoning, or other types of embedded bias. In many ways, this mirrors the risks of social engineering traditionally faced by humans. Even without deliberate or malicious efforts to corrupt them, AI systems and AI agents can carry out unintended actions; creating vulnerabilities and opportunities for insider harm.

How to defend against AI-powered insider threats

The increasing attack surfaces created or facilitated by AI is a growing concern.  In Darktrace’s own AI cybersecurity research, the risks introduced, and acknowledged, through the proliferation of AI tools and systems continues to outstrip traditional policies and governance guardrails. 22% of respondents in the survey cited ‘insider misuse aided by generative AI’ as a major threat concern.  And yet, in the same survey, only 37% of all respondents have formal policies in place to manage the safe and responsible use of AI.  This draws a significant and worrying delta between the known risks and threat concerns, and the ability (and resources) to mitigate them.

What can CISOs and SOC leaders do to protect their organization from AI insider threats?  

Given the rapid adaptation, adoption, and scale of AI systems, implementing the right levels of AI governance is non-negotiable. Getting the correct balance between AI-driven productivity gains and careful compliance will lead to long-term benefits. Adapting traditional insider threat structures to account for newer risks posed through the use of AI will be crucial. And understanding the value of AI systems that add to your cybersecurity resilience rather than imperil it will be essential.

For those responsible for the security and protection of their business assets and data holdings, the way AI has changed the paradigm of insider threats can seem daunting.  Adopting strong, and suitable AI governance can become difficult to introduce due to the volume and complexity of systems needed to be monitored. As well as traditional insider threat mitigations such as user monitoring, access controls and active management, the speed and autonomy of some AI systems need different, as well as additional layers of control.  

How Darktrace helps protect against AI-powered insider threats

Darktrace has demonstrated that, through platforms such as our proprietary Cyber AI Analyst, and our latest product Darktrace / SECURE AI, there are ways AI systems can be self-learning, self-critical and resilient to unpredictable AI behavior whilst still offering impressive returns; complementing traditional SOC and CISO strategies to combat insider threat.  

With / SECURE AI, some of the ephemeral risks drawn through AI use can be more easily governed.  Specifically, the ability to monitor conversational prompts (which can both affect AI outputs as well as highlight potential attempts at manipulation of AI; raising early flags of insider intent); the real-time observation of AI usage and development (highlighting potential blind-spots between AI development and deployment); shadow AI detection (surfacing unapproved tools and agents across your IT stack) and; the ability to know which identities (human or non-human) have permission access. All these features build on the existing foundations of strong insider threat management structures.  

How to take a defense-in-depth approach to AI-powered insider threats

Even without these tools, there are four key areas where robust, more effective controls can mitigate AI-powered insider threat.  Each of the below offers a defencce-in-depth approach: layering acknowledgement and understanding of an insider vector with controls that can bolster your defenses.  

Identity and access controls

Having a clear understanding of the entities that can access your sensitive information, assets and personnel is the first step in understanding the landscape in which insider harm can occur.  AI has shown that it is not just flesh and bone operators who can administer insider threats; Non-Human Identities (such as agentic AI systems) can operate with autonomy and freedom if they have the right credentials. By treating NHIs in the same way as human operators (rather than helpful machine-based tools), and adding similar mitigation and management controls, you can protect both your business, and your business-based identities from insider-related attention.

Visibility and shadow AI detection

Configuring AI systems carefully, as well as maintaining internal monitoring, can help identify ‘shadow AI’ usage; defined as the use of unsanctioned AI tools within the workplace1 (this topic was researched in Darktrace’s own paper on "How to secure AI in the enterprise". The adoption of shadow AI could be the result of deliberate preference, or ‘shortcutting’; where individuals use systems and models they are familiar with, even if unsanctioned. As well as some performance risks inherent with the use of shadow AI (such as data leakage and unwanted actions), it could also be a dangerous precursor for insider-related harm (either through deliberate attempts to subvert regular monitoring, or by opening vulnerabilities through unpatched or unaccredited tooling).

Prompt and Output Guardrails

The ability to introduce guardrails for AI systems offers something of a traditional “perimeter protection” layer in AI defense architecture; checking prompts and outputs against known threat vectors, or insider threat methodologies. Alone, such traditional guardrails offer limited assurance.  But, if tied with behavior-centric threat detection, and an enforcement system that deters both malicious and accidental insider activities, this would offer considerable defense- in- depth containment.  

Forensic logging and incident readiness response

The need for detection, data capture, forensics, and investigation are inherent elements of any good insider threat strategy. To fully understand the extent or scope of any suspected insider activity (such as understanding if it was deliberate, targeted, or likely to occur again), this rich vein of analysis could prove invaluable.  As the nature of business increasingly turns ephemeral; with assets secured in remote containers, information parsed through temporary or cloud-based architecture, and access nodes distributed beyond the immediate visibility of internal security teams, the development of AI governance through containment, detection, and enforcement will grow ever more important.

Enabling these controls can offer visibility and supervision over some of the often-expressed risks about AI management. With the right kind of data analytics, and with appropriate human oversight for high-risk actions, it can illuminate the core concerns expressed through a new paradigm of AI-powered insider threats by:

  • Ensuring deliberately mis-configured AI systems are exposed through regular monitoring.
  • Highlighting changes in systems-based activity that might indicate harmful insider actions; whether malicious or accidental.
  • Promoting a secure-by-design process that discourages and deters insider-related ambitions.
  • Ensuring the control plane for identity-based access spans humans, NHIs and AI models, and:
  • Offering positive containment strategies that will help curate the extent of AI control, and minimize unwanted activities.

Why insider threat remains a human challenge

At its root, and however it has been configured, AI is still an algorithmic tool; something designed to automate, process and manage computational functions at machine speed, and boost productivity.  Even with the best cybersecurity defenses in place, the success of an insider threat management program will still depend on the ability of human operators to identify, triage, and manage the insider threat attack surface.  

AI governance policies, human-in-the-loop break points, and automated monitoring functions will not guard against acts of insider harm unless there is intention to manage this proactively, and through a strong culture of how to guard against abuses of trust and responsibility.

[related-resource]

Continue reading
About the author
Jason Lusted
AI Governance Advisor

Blog

/

Network

/

May 18, 2026

中国系APTキャンペーン、アップデートされたFDMTPバックドアで企業を狙う

Default blog imageDefault blog image

ダークトレースは、中国系グループの活動と一致する動きを特定しました。これは、主にアジア太平洋および日本(APJ)地域の顧客環境を標的としたTwill Typhoonに関連するキャンペーンです。

2025年9月下旬から、影響を受けた複数のホストが、YahooやApple関連のサービスを装ったインフラを含む、コンテンツ配信ネットワーク(CDN)を偽装したドメインへのリクエストを行っていることが観察されました。これらの事例において、ダークトレースは一貫した動作のパターンを特定しました。それは、正当なバイナリと悪意あるダイナミックリンクライブラリ(DLL)を同時に取得し、モジュラー型の.NETベースのリモートアクセス型トロイの木馬(RAT)フレームワークのサイドローディングと実行を可能にするものでした。

これらはダークトレースが先日発表した中国系オペレーションについてのレポート、 Crimson Echoで説明されているパターンとも一致しています。このケースでは、正規のソフトウェア上にモジュラー型の侵入チェーンが構築され、ステージングされたペイロードの投下が見られました。脅威アクターは正当なバイナリをコンフィギュレーションファイルや悪意あるDLLとともに取得することにより、.NETベースのRATのサイドローディングを可能にしました。

キャンペーンの確認

これらのケースには同じ順序のシーケンスが現れています:(1) 正規の実行可能ファイルの取得、(2) 対応する .config ファイルの取得、(3) 悪意あるDLLの取得、(4) DLLの繰り返しダウンロード、(5) コマンド&コントロール(C2)通信。 正規のバイナリは正規のプロセスを提供しますが、.config ファイルは悪意あるバイナリを取得します。

ダークトレースは、この活動が公に報告されているTwill Typhoonの手法と一致していると中程度の確信を持って評価しています。FDMTPの使用、DLLサイドローディング、および重複するインフラストラクチャが観察されたことは、以前に見られた作戦と一致していますが、これは特定の単一のアクターに固有のものではありません。アトリビューションには可視性による制限があります。初期アクセスは直接確認されませんでしたが、侵入のパターンは同様の作戦で報告されている既知のフィッシングによる侵入手法と一致しています。

Darktraceによる観測

2025年9月下旬より、Darktraceは複数の顧客環境において良く知られたプラットフォームの“CDN”エンドポイントと称するインフラ(YahooやAppleを偽装したものを含む)に対してHTTP GETリクエストが行われていることを観測しました。これらのケースでは、影響を受けたホストは正当な実行形式、対応する.configファイル(同じベース名)、そしてサイドローディング用DLLを取得しています。正当なバイナリ+コンフィギュレーション+DLLのシーケンスは中国系の攻撃キャンペーンで見られているものです。

いくつかのケースでは、ホストはさらに/GetClusterエンドポイントへのアウトバウンドリクエストを発行しており、protocol=Dotnet-Tcpdmtpパラメータも含まれていました。このアクティビティの後繰り返しDLLコンテンツの取得が行われ、その後これが正当なプロセス内でサーチオーダー杯ジャッキングに使われました。

2025年9月~10月に見られた多くのケースで、Darktraceのアラートは初期段階の登録およびC2セットアップ動作を識別しました。その後同じ外部ホストからのDLL(Client.dll等)取得(一部のケースでは複数日に渡って繰り返し)が続き、これは実行チェーンの確立と維持を示すものでした。2026年4月、金融セクターの顧客のエンドポイントがyahoo-cdn[.]it[.]comに対して一連のGETリクエストを開始し、最初に正当なバイナリ(vshost.exeおよびdfsvc.exeを含む)を取得し、その後11日間にわたり関連するコンフィギュレーションファイルおよびDLLコンポーネント(dfsvc.exe.configおよびdnscfg.dllを含む)を繰り返し取得しました。Visual Studio ホスティングと OneClick(dfsvc.exe)のパスの使用はどちらも、マルウェアをターゲット環境で実行できるようにするためのものです。

技術分析

初期ステージングおよび実行

最初のアクセスはわかっていませんが、ダークトレースの研究者はマルウェアを含む複数のアーカイブを特定しました。

代表的なサンプルには以下を含むZIPアーカイブ(“test.zip”)が含まれていました:

  • 正規の実行形式:biz_render.exe(Sogou Pinyin IME)
  • 悪意あるDLL: browser_host.dll

"test.zip" という名前のzipアーカイブには、正規のバイナリ"biz_render.exe" が含まれており、これは人気のある中国語IMEであるSogou Pinyinです。

正規のバイナリと共に ”browser_host.dll” という悪意のあるDLLがあります。</x1>この正規のバイナリは ”browser_host.dll”という正規のDLLを、LoadLibraryExWを介して読み込みますが、悪意のあるDLLにも同じ名前がつけられることにより、biz_render.exeに悪意のあるDLLをサイドロードします。同名の悪意あるDLLを提供することで、攻撃者は実行フローを乗っ取り、信頼されたプロセス内でペイロードを実行することができます。

図1.Biz_render.exe による browser_host.dll のローディング

正規のバイナリは、サイドロードされた"browser_host.dll"から関数GetBrowserManagerInstanceを呼び出し、その後、埋め込まれた文字列に対してXORベースの復号化(キー 0x90)を実行して、mscoree.dllを解決し動的にロードします。

このDLLは、ネイティブバイナリのみに依存するのではなく、Windowsの共通言語ランタイム(CLR)を使用することにより、プロセス内で管理された.NETコードを実行します。実行中、ローダーはペイロードを.NETアセンブリとして直接メモリにロードし、メモリ内での実行を可能にします。

C2 登録

GETリクエストが以下に対して実行されます:

GET /GetCluster?protocol=DotNet-TcpDmtp&tag={0}&uid={1}

カスタムヘッダ:

Verify_Token: Dmtp

これは、後の通信に使用されるIPアドレスをbase64でエンコードし、gzipで圧縮したものを返します。

図2.デコードされたIP

ステージングされたペイロードの取得

その後のアクティビティには、yahoo-cdn.it[.]comからの複数のコンポーネントの取得が含まれます。以下のGETリクエストが行われます:

/dfsvc.exe

/dnscfg.dll

/dfsvc.exe.config

/vhost.exe

/Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll

/config.etl

ClickOnceおよびAppDomainのハイジャッキング

Dfsvc.exeは正当なWindowsのClickOnceエンジンであり、ClickOnceアプリケーションの更新に使用される.NETフレームワークの一部です。付随するdfsvc.exeには、アプリケーションのコンフィギュレーションデータを保存するために使用されるdfsvc.exe.configファイルが含まれています。しかし、このケースではマルウェアが正規のdfsvc.exe.configをC:\Windows\Microsoft.NET\Framework64\v4.0.30319のサーバーから取得したものと置き換えます。

さらに、正当なVisual Studioホスティングプロセスであるvhost.exeがサーバーから取得され、それとともに”Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll”と”config.etl”も取得されます。このDLLは、config.etl内のAESで暗号化されたペイロードを復号してロードするために使用されます。暗号化されたペイロードはdnscfg.dllであり、これはdfsvcの代わりにvshostにロードすることができ、環境が.NETをサポートしていない場合に使用することができます。

図3.ClickOnceのコンフィギュレーション

悪意あるコンフィギュレーションはログ記録を無効にし、アプリケーションがリモートサーバーからdnscfg.dllを読み込むようにし、カスタムのAppDomainManagerを使用してdfsvc.exeの初期化時にDLLが実行されるようにします。永続性を確保するために、%APPDATA%\Local\Microsoft\WindowsApps\dfsvc.exeのスケジュールされたタスクが追加されます。

コアペイロード

DLL dnscfg.dll は、カスタムTCPベースのプロトコルであるDMTP(Duplex Message Transport Protocol)を使用して通信する、著しく難読化された.NET RAT(Client.TcpDmtp.dll) です。 観察された特徴から、これはFDMTPフレームワーク(v3.2.5.1)の更新版であると思われます。

図4.InitializeNewDomain

ペイロードは:

  • クラスタベースの解決を使用 (GetHostFromCluster)
  • トークン検証を実装
  • 永続的な実行ループに入る (LoopMessage)
  • DMTPを介した構造化されたリモートタスキングをサポート

接続が確立されると、マルウェアは永続的なループ(LoopMessage)に入り、リモートサーバーからのコマンドを受信できるようになります。

図5.DMTP接続関数

値は直接参照するのではなく、実行時に解決されるコンテナを通じて取得されます。文字列値は暗号化されたバイト配列(_0)に格納され、カスタムのXORベースの文字列復号ルーチン(dcsoft)によって復号されます。キーの下位16ビットは0xA61D(42525)とXORされて初期のXORキーが導出され、それに続くビットは文字列の長さと暗号化されたバイト配列へのオフセットを定義します。各文字は2つの暗号化されたバイトから再構成され、増加するキー値とXORされて、ペイロードで使用される平文文字列が生成されます。

図6.復号化された文字列

リソースセクションには複数の圧縮されたバイナリが埋め込まれており、その大多数はライブラリファイルです。

図7: リソース

モジュラー型フレームワークとプラグイン

ペイロードには以下を含む複数の圧縮ライブラリが埋め込まれています:

  • client.core.dll
  • client.dmtpframe.dll

Client.core.dllは、システムプロファイリング、C2通信、およびプラグイン実行に使用されるコアライブラリです。インプラントは、アンチウイルス製品、ドメイン名、HWID、CLRバージョン、管理者権限、ハードウェアの詳細、ネットワークの詳細、オペレーティングシステム、およびユーザーを含む情報を取得する機能を備えています。

図8: Client.Core.Info 関数

さらに、このコンポーネントはプラグインの読み込みを担当しており、バイナリおよびJSONベースのプラグイン実行の両方をサポートしています。これにより、プラグインは実行されるタスクに応じて異なる形式のコマンドやパラメータを受け取ることができます。

このフレームワークがプラグインのハッシュ、メソッド名、タスク識別子、呼び出し元追跡、引数の処理などの詳細を管理し、プラグインを環境内で一貫して実行することができます。実行管理に加えて、このライブラリはログ記録、通信、プロセス処理などの共通のランタイム機能へのアクセスをプラグインに提供します。

図9: Client.core 関数

client.dmtpframe.dllは次を処理します:

  • DMTP通信
  • ハートビートおよび再接続
  • レジストリを通じたプラグイン永続化:

HKCU\Software\Microsoft\IME\{id}

Client.dmtpframe.dllはTouchSocket DMTPネットワーキングライブラリ上に構築されており、リモートプラグインの管理を行います。このDLLは、ハートビートの維持、再接続処理、RPCスタイルのメッセージング、SSLサポート、およびトークンベースの認証を含むリモート通信機能を実装しています。このDLLは、永続化のためにHKCU/Software/Microsoft/IME/{id} のレジストリにプラグインを追加する機能も備えています。  

観測されたプラグイン

使用されたすべてのプラグインは判明していませんが、研究者たちは以下の4つを確認することができました:

  • Persist.WpTask.dll - リモートでスケジュールされたWindowsタスクを作成、削除、トリガーするために使用されます。
  • Persist.registry.dll - レジストリの永続性を管理するために使用され、レジストリ値の作成および削除、隠し永続化キーの操作が可能です。
  • Persist.extra.dll - メインフレームワークの読み込みと永続化に使用されます。
  • Assist.dll - リモートでファイルやコマンドを取得したり、システムプロセスを操作したりするために使用されます。
図10: IME レジストリに格納されたプラグイン
図11: プラグインリソース内の難読化されたスクリプト

Persist.extra.dll は、スクリプト"setup.log"を、読み込みメインフレームワークをロードおよび永続化するために使用されるモジュールです。バイナリのリソースセクションに格納されている難読化されたスクリプトは、.NET COMオブジェクトを作成し、永続化のためにレジストリキーHKCU\Software\Classes\TypeLib\ {9E175B61-F52A-11D8-B9A5-505054503030}\1.0\1\Win64 に追加します。このスクリプトの難読化を解除すると、"WindowsBase.dll”という別のDLLが明らかになります。

図12: スクリプトのレジストリエントリ

バイナリは5分ごとにicloud-cdn[.]netをチェックし、バージョン文字列を取得し、暗号化されたペイロードであるchecksum.binをダウンロードし、ローカルにC:\ProgramData\USOShared\Logs\checksum.etlとして保存し、ハードコードされたキーPOt_L[Bsh0=+@0a.を使用してAESで復号化し、Assembly.Load(byte[])を介して復号化されたアセンブリをメモリから直接ロードします。version.txtファイルは更新マーカーとして機能し、リモートのバージョンが変更された場合にのみ再ダウンロードされるようにします。また、ミューテックスは重複したインスタンスの起動を防ぎます。

図13: USOShared/Logs.

Checksum.etlはAESで復号化され、メモリにロードされ、別の.NET DLLである"Client.dll"がロードされます。このバイナリは前述の"dnscfg.dll"と同じものであり、脅威アクターがバージョンに基づいてメインフレームワークを更新することを可能にします。

まとめ

これらの事例で一貫して観測されたシーケンスは以下の通りです:

  • 正規の実行形式の取得
  • サイドローディング用DLLの取得
  • /GetClusterによるC2登録

侵入は単一の足場に依存しておらず、独立して更新、交換、再読み込みが可能なコンポーネントに分散されています。このアプローチは、中国系脅威アクターの手法と一致しています。Crimson Echoレポートで説明されているように、安定した特徴は技術的なものではなく、動作上の特徴です。インフラストラクチャは変化し、ペイロードも変わりますが、実行モデルは同じです。防御者にとって、その意味は明白です。それは個別の指標に基づく検知は急速に劣化するということです。動作のシーケンスや、アクセスがどのように構築され再確立されるかに基づく検知は、はるかに永続的です。

協力:Tara Gould (Malware Research Lead), Adam Potter (Senior Cyber Analyst), Emma Foulger (Global Threat Research Operations Lead), Nathaniel Jones (VP, Security & AI Strategy)

編集: Ryan Traill (Content Manager)


付録

検知モデルとトリガーされたインジケータのリストをIOCとともに提示します。

Indicators of Compromise (IoCs)

Test.zip - fc3959ebd35286a82c662dc81ca658cb

Dnscfg.dll - b2c8f1402d336963478f4c5bc36c961a

Client.TcpDmtp.dll - c52b4a16d93a44376f0407f1c06e0b

Browser_host.dll - c17f39d25def01d5c87615388925f45a

Client.DmtpFrame.dll - 482cc72e01dfa54f30efe4fefde5422d

Persist.Extra - 162F69FE29EB7DE12B684E979A446131

Persist.Registry - 067FBAD4D6905D6E13FDC19964C1EA52

Assist - 2CD781AB63A00CE5302ED844CFBECC27

Persist.WpTask - DF3437C88866C060B00468055E6FA146

Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll - c650a624455c5222906b60aac7e57d48

www.icloud-cdn[.]net

www.yahoo-cdn.it[.]com

154.223.58[.]142[AP8] [EF9]

MITRE ATT&CK テクニック

T1106 – ネイティブAPI

T1053.005 -スケジュールされたタスク

T1546.16 - コンポーネントオブジェクトモデルハイジャッキング

T1547.001 – レジストリ実行キー

T1511.001 -DLLインジェクション

T1622 – デバッガ回避

T1027 – ファイルおよび情報の難読化解除/復号化解除

T1574.001 - 実行フローハイジャック:DLL

T1620 – リフレクティブコードローディング

T1082 – システム情報探索

T1007 – システムサービス探索

T1030 – システムオーナー/ユーザー探索

T1071.001 - Webプロトコル

T1027.007 - 動的API解決

T1095 – 非アプリケーションレイヤプロトコル

Darktrace モデルアラート

·      Compromise / Beaconing Activity To External Rare

·      Compromise / HTTP Beaconing to Rare Destination

·      Anomalous File / Script from Rare External Location

·      Compromise / Sustained SSL or HTTP Increase

·      Compromise / Agent Beacon to New Endpoint

·      Anomalous File / EXE from Rare External Location

·      Anomalous File / Multiple EXE from Rare External Locations

·      Compromise / Quick and Regular Windows HTTP Beaconing

·      Compromise / High Volume of Connections with Beacon Score

·      Anomalous File / Anomalous Octet Stream (No User Agent)

·      Compromise / Repeating Connections Over 4 Days

·      Device / Large Number of Model Alerts

·      Anomalous Connection / Multiple Connections to New External TCP Port

·      Compromise / Large Number of Suspicious Failed Connections

·      Anomalous Connection / Multiple Failed Connections to Rare Endpoint

·      Device / Increased External Connectivity

Continue reading
About the author
Tara Gould
Malware Research Lead
あなたのデータ × DarktraceのAI
唯一無二のDarktrace AIで、ネットワークセキュリティを次の次元へ