ブログ
/
Network
/
November 27, 2023

Detecting PurpleFox Rootkit with Darktrace AI

The PurpleFox rootkit poses significant risks. Discover how Darktrace leveraged advanced techniques to combat this persistent cyber threat.
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
Piramol Krishnan
Cyber Security Analyst
Default blog image
27
Nov 2023

Versatile Malware: PurpleFox

As organizations and security teams across the world move to bolster their digital defenses against cyber threats, threats actors, in turn, are forced to adopt more sophisticated tactics, techniques and procedures (TTPs) to circumvent them. Rather than being static and predictable, malware strains are becoming increasingly versatile and therefore elusive to traditional security tools.

One such example is PurpleFox. First observed in 2018, PurpleFox is a combined fileless rootkit and backdoor trojan known to target Windows machines. PurpleFox is known for consistently adapting its functionalities over time, utilizing different infection vectors including known vulnerabilities (CVEs), fake Telegram installers, and phishing. It is also leveraged by other campaigns to deliver ransomware tools, spyware, and cryptocurrency mining malware. It is also widely known for using Microsoft Software Installer (MSI) files masquerading as other file types.

The Evolution of PurpleFox

The Original Strain

First reported in March 2018, PurpleFox was identified to be a trojan that drops itself onto Windows machines using an MSI installation package that alters registry values to replace a legitimate Windows system file [1]. The initial stage of infection relied on the third-party toolkit RIG Exploit Kit (EK). RIG EK is hosted on compromised or malicious websites and is dropped onto the unsuspecting system when they visit browse that site. The built-in Windows installer (MSIEXEC) is leveraged to run the installation package retrieved from the website. This, in turn, drops two files into the Windows directory – namely a malicious dynamic-link library (DLL) that acts as a loader, and the payload of the malware. After infection, PurpleFox is often used to retrieve and deploy other types of malware.  

Subsequent Variants

Since its initial discovery, PurpleFox has also been observed leveraging PowerShell to enable fileless infection and additional privilege escalation vulnerabilities to increase the likelihood of successful infection [2]. The PowerShell script had also been reported to be masquerading as a .jpg image file. PowerSploit modules are utilized to gain elevated privileges if the current user lacks administrator privileges. Once obtained, the script proceeds to retrieve and execute a malicious MSI package, also masquerading as an image file. As of 2020, PurpleFox no longer relied on the RIG EK for its delivery phase, instead spreading via the exploitation of the SMB protocol [3]. The malware would leverage the compromised systems as hosts for the PurpleFox payloads to facilitate its spread to other systems. This mode of infection can occur without any user action, akin to a worm.

The current iteration of PurpleFox reportedly uses brute-forcing of vulnerable services, such as SMB, to facilitate its spread over the network and escalate privileges. By scanning internet-facing Windows computers, PurpleFox exploits weak passwords for Windows user accounts through SMB, including administrative credentials to facilitate further privilege escalation.

Darktrace detection of PurpleFox

In July 2023, Darktrace observed an example of a PurpleFox infection on the network of a customer in the healthcare sector. This observation was a slightly different method of downloading the PurpleFox payload. An affected device was observed initiating a series of service control requests using DCE-RPC, instructing the device to make connections to a host of servers to download a malicious .PNG file, later confirmed to be the PurpleFox rootkit. The device was then observed carrying out worm-like activity to other external internet-facing servers, as well as scanning related subnets.

Darktrace DETECT™ was able to successfully identify and track this compromise across the cyber kill chain and ensure the customer was able to take swift remedial action to prevent the attack from escalating further.

While the customer in question did have Darktrace RESPOND™, it was configured in human confirmation mode, meaning any mitigative actions had to be manually applied by the customer’s security team. If RESPOND had been enabled in autonomous response mode at the time of the attack, it would have been able to take swift action against the compromise to contain it at the earliest instance.

Attack Overview

Figure 1: Timeline of PurpleFox malware kill chain.

Initial Scanning over SMB

On July 14, 2023, Darktrace detected the affected device scanning other internal devices on the customer’s network via port 445. The numerous connections were consistent with the aforementioned worm-like activity that has been reported from PurpleFox behavior as it appears to be targeting SMB services looking for open or vulnerable channels to exploit.

This initial scanning activity was detected by Darktrace DETECT, specifically through the model breach ‘Device / Suspicious SMB Scanning Activity’. Darktrace’s Cyber AI Analyst™ then launched an autonomous investigation into these internal connections and tied them into one larger-scale network reconnaissance incident, rather than a series of isolated connections.

Figure 2: Cyber AI Analyst technical details summarizing the initial scanning activity seen with the internal network scan over port 445.

As Darktrace RESPOND was configured in human confirmation mode, it was unable to autonomously block these internal connections. However, it did suggest blocking connections on port 445, which could have been manually applied by the customer’s security team.

Figure 3: The affected device’s Model Breach Event Log showing the initial scanning activity observed by Darktrace DETECT and the corresponding suggested RESPOND action.

Privilege Escalation

The device successfully logged in via NTLM with the credential, ‘administrator’. Darktrace recognized that the endpoint was external to the customer’s environment, indicating that the affected device was now being used to propagate the malware to other networks. Considering the lack of observed brute-force activity up to this point, the credentials for ‘administrator’ had likely been compromised prior to Darktrace’s deployment on the network, or outside of Darktrace’s purview via a phishing attack.

Exploitation

Darktrace then detected a series of service control requests over DCE-RPC using the credential ‘admin’ to make SVCCTL Create Service W Requests. A script was then observed where the controlled device is instructed to launch mshta.exe, a Windows-native binary designed to execute Microsoft HTML Application (HTA) files. This enables the execution of arbitrary script code, VBScript in this case.

Figure 4: PurpleFox remote service control activity captured by a Darktrace DETECT model breach.
Figure 5: The infected device’s Model Breach Event Log showing the anomalous service control activity being picked up by DETECT.

There are a few MSIEXEC flags to note:

  • /i : installs or configures a product
  • /Q : sets the user interface level. In this case, it is set to ‘No UI’, which is used for “quiet” execution, so no user interaction is required

Evidently, this was an attempt to evade detection by endpoint users as it is surreptitiously installed onto the system. This corresponds to the download of the rootkit that has previously been associated with PurpleFox. At this stage, the infected device continues to be leveraged as an attack device and scans SMB services over external endpoints. The device also appeared to attempt brute-forcing over NTLM using the same ‘administrator’ credential to these endpoints. This activity was identified by Darktrace DETECT which, if enabled in autonomous response mode would have instantly blocked similar outbound connections, thus preventing the spread of PurpleFox.

Figure 6: The infected device’s Model Breach Event Log showing the outbound activity corresponding to PurpleFox’s wormlike spread. This was caught by DETECT and the corresponding suggested RESPOND action.

Installation

On August 9, Darktrace observed the device making initial attempts to download a malicious .PNG file. This was a notable change in tactics from previously reported PurpleFox campaigns which had been observed utilizing .MOE files for their payloads [3]. The .MOE payloads are binary files that are more easily detected and blocked by traditional signatured-based security measures as they are not associated with known software. The ubiquity of .PNG files, especially on the web, make identifying and blacklisting the files significantly more difficult.

The first connection was made with the URI ‘/test.png’.  It was noted that the HTTP method here was HEAD, a method similar to GET requests except the server must not return a message-body in the response.

The metainformation contained in the HTTP headers in response to a HEAD request should be identical to the information sent in response to a GET request. This method is often used to test hypertext links for validity and recent modification. This is likely a way of checking if the server hosting the payload is still active. Avoiding connections that could possibly be detected by antivirus solutions can help keep this activity under-the-radar.

Figure 7: Packet Capture from an affected customer device showing the initial HTTP requests to the payload server.
Figure 8: Packet Capture showing the HTTP requests to download the payloads.

The server responds with a status code of 200 before the download begins. The HEAD request could be part of the attacker’s verification that the server is still running, and that the payload is available for download. The ‘/test.png’ HEAD request was sent twice, likely for double confirmation to begin the file transfer.

Figure 9: PCAP from the affected customer device showing the Windows Installer user-agent associated with the .PNG file download.

Subsequent analysis using a Packet Capture (PCAP) tool revealed that this connection used the Windows Installer user agent that has previously been associated with PurpleFox. The device then began to download a payload that was masquerading as a Microsoft Word document. The device was thus able to download the payload twice, from two separate endpoints.

By masquerading as a Microsoft Word file, the threat actor was likely attempting to evade the detection of the endpoint user and traditional security tools by passing off as an innocuous text document. Likewise, using a Windows Installer user agent would enable threat actors to bypass antivirus measures and disguise the malicious installation as legitimate download activity.  

Darktrace DETECT identified that these were masqueraded file downloads by correctly identifying the mismatch between the file extension and the true file type. Subsequently, AI Analyst was able to correctly identify the file type and deduced that this download was indicative of the device having been compromised.

In this case, the device attempted to download the payload from several different endpoints, many of which had low antivirus detection rates or open-source intelligence (OSINT) flags, highlighting the need to move beyond traditional signature-base detections.

Figure 10: Cyber AI Analyst technical details summarizing the downloads of the PurpleFox payload.
Figure 11 (a): The Model Breach generated by the masqueraded file transfer associated with the PurpleFox payload.
Figure 11 (b): The Model Breach generated by the masqueraded file transfer associated with the PurpleFox payload.

If Darktrace RESPOND was enabled in autonomous response mode at the time of the attack it would have acted by blocking connections to these suspicious endpoints, thus preventing the download of malicious files. However, as RESPOND was in human confirmation mode, RESPOND actions required manual application by the customer’s security team which unfortunately did not happen, as such the device was able to download the payloads.

Conclusion

The PurpleFox malware is a particularly dynamic strain known to continually evolve over time, utilizing a blend of old and new approaches to achieve its goals which is likely to muddy expectations on its behavior. By frequently employing new methods of attack, malicious actors are able to bypass traditional security tools that rely on signature-based detections and static lists of indicators of compromise (IoCs), necessitating a more sophisticated approach to threat detection.  

Darktrace DETECT’s Self-Learning AI enables it to confront adaptable and elusive threats like PurpleFox. By learning and understanding customer networks, it is able to discern normal network behavior and patterns of life, distinguishing expected activity from potential deviations. This anomaly-based approach to threat detection allows Darktrace to detect cyber threats as soon as they emerge.  

By combining DETECT with the autonomous response capabilities of RESPOND, Darktrace customers are able to effectively safeguard their digital environments and ensure that emerging threats can be identified and shut down at the earliest stage of the kill chain, regardless of the tactics employed by would-be attackers.

Credit to Piramol Krishnan, Cyber Analyst, Qing Hong Kwa, Senior Cyber Analyst & Deputy Team Lead, Singapore

Appendices

Darktrace Model Detections

  • Device / Increased External Connectivity
  • Device / Large Number of Connections to New Endpoints
  • Device / SMB Session Brute Force (Admin)
  • Compliance / External Windows Communications
  • Anomalous Connection / New or Uncommon Service Control
  • Compromise / Unusual SVCCTL Activity
  • Compromise / Rare Domain Pointing to Internal IP
  • Anomalous File / Masqueraded File Transfer

RESPOND Models

  • Antigena / Network / Significant Anomaly / Antigena Breaches Over Time Block
  • Antigena / Network / External Threat / Antigena Suspicious Activity Block
  • Antigena / Network / Significant Anomaly / Antigena Significant Anomaly from Client Block
  • Antigena / Network / Significant Anomaly / Antigena Enhanced Monitoring from Client Block
  • Antigena / Network / External Threat / Antigena Suspicious File Block
  • Antigena / Network / External Threat / Antigena File then New Outbound Block

List of IoCs

IoC - Type - Description

/C558B828.Png - URI - URI for Purple Fox Rootkit [4]

5b1de649f2bc4eb08f1d83f7ea052de5b8fe141f - File Hash - SHA1 hash of C558B828.Png file (Malware payload)

190.4.210[.]242 - IP - Purple Fox C2 Servers

218.4.170[.]236 - IP - IP for download of .PNG file (Malware payload)

180.169.1[.]220 - IP - IP for download of .PNG file (Malware payload)

103.94.108[.]114:10837 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

221.199.171[.]174:16543 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

61.222.155[.]49:14098 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

178.128.103[.]246:17880 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

222.134.99[.]132:12539 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

164.90.152[.]252:18075 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

198.199.80[.]121:11490 - IP - IP from Service Control MSIEXEC script to download PNG file (Malware payload)

MITRE ATT&CK Mapping

‍Tactic - Technique

Reconnaissance - Active Scanning T1595, Active Scanning: Scanning IP Blocks T1595.001, Active Scanning: Vulnerability Scanning T1595.002

Resource Development - Obtain Capabilities: Malware T1588.001

Initial Access, Defense Evasion, Persistence, Privilege Escalation - Valid Accounts: Default Accounts T1078.001

Initial Access - Drive-by Compromise T1189

Defense Evasion - Masquerading T1036

Credential Access - Brute Force T1110

Discovery - Network Service Discovery T1046

Command and Control - Proxy: External Proxy T1090.002

References

  1. https://blog.360totalsecurity.com/en/purple-fox-trojan-burst-out-globally-and-infected-more-than-30000-users/
  2. https://www.trendmicro.com/en_us/research/19/i/purple-fox-fileless-malware-with-rookit-component-delivered-by-rig-exploit-kit-now-abuses-powershell.html
  3. https://www.akamai.com/blog/security/purple-fox-rootkit-now-propagates-as-a-worm ‍
  4. https://www.foregenix.com/blog/an-overview-on-purple-fox ‍
  5. https://www.trendmicro.com/en_sg/research/21/j/purplefox-adds-new-backdoor-that-uses-websockets.html
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
Piramol Krishnan
Cyber Security Analyst

More in this series

No items found.

Blog

/

AI

/

October 26, 2026

PHP脆弱性、ARTEX、そしてサイバー攻撃におけるAIの役割拡大

Default blog imageDefault blog image

BCVE-2026-109618およびCVE-2026-109619の公開により、PHPを運用している組織は緊急対応を余儀なくされました。どちらの脆弱性も許可のないリモートコード実行を可能にするものであり、対象はPHPが組み込まれ、サードパーティベンダーにアップデートを依存する製品およびアプライアンスも含まれていました[1]。

初期のガイダンスではインターネットに接続されたシステムにパッチを適用し、予期しないコマンド実行やWebroot変更、PHPサーバーからのアウトバウンド接続など、エクスプロイトの成功に関連した振る舞いを監視することに重点が置かれました。

Darktraceは監視中の環境においてスキャニングが広範に発生していることを観測し、これにはPHP脆弱性を標的としたアクティビティに関連すると報告されている数百の個別のIPアドレスが関係していました。スキャニングの量はエクスプロイトの成功を示す証拠の数を著しく上回るものでした。アナリストにとってはこの違いが重要です。スキャニングは露出したインフラへの関心を表すものです。侵害を確認するには、標的とされたシステム上でこれに続く振る舞い、たとえばコマンド実行、ファイル変更、予期しないアウトバウンド接続などの証拠が必要です。

PHPは例外的なケースではありません。その後、Imperva社が脆弱なNode.jsビルドに対するリモートコード実行を悪意あるBrotliデータを通じて実証し、圧縮HTTPレスポンスおよび設定済みリクエストパーサーを通じたコード実行を再現しました。同じ入力はパッチ適用済みのランタイムからは拒否されました。Imperva社はNode2ShellおよびPHP2Shellに対する研究結果を、脆弱性探索とエクスプロイト開発スピードの上昇と結びつけています。[2]

DarktraceはCVE-2026-109618あるいはCVE-2026-109619エクスプロイトの直接的証拠を観測していませんが、10月21日にゼロデイエクスプロイトのアクティビティと一致する過去6か月間で最大の脅威検知を観測し、これは過去のデータと比較して64%上昇を示すものでした。この上昇とPHP脆弱性との関連性は確認されていません。Darktraceの振る舞いベースのアプローチは、特定のエクスプロイトに対して記述されたルールだけに頼ることなく異常なアクティビティを検知するよう設計されています。同様の検知の増加はLog4j脆弱性の公表、およびその他の世界的に重大な脆弱性公表時にも観測されています。

AI支援による脆弱性探索

AIシステムが高い脆弱性探索能力を持つようになるなかで、PHPの脆弱性が発見されました[3]。OpenAIは2026年6月にDaybreakプログラムを発表し、GPT-5.5-CyberおよびCodex Securityをセキュリティ研究者やソフトウェア維持管理者とのパートナーシップと結びつけました。OpenAIはこれらのモデルがブラウザ、ネットワークインフラ、FreeBSDおよびLinuxカーネルの脆弱性の発見およびパッチ作成に適用されていると説明しています。ダークトレースは6月にOpenAI Daybreak Cyber Partner Programに参加し、OpenAIの提供するサイバー能力をDarktrace製品およびサービスにどのように統合できるかを研究しています [4][10]。

OpenAIは8月に、Codex Security Cloudが30,000以上のコードベースにおいて3000万件以上のコミットを分析したと報告しています。OpenAIによると、Cloudflare社はDaybreakを通じてアクセスするモデルを利用して、顧客の承認を受けたコードを調査し、その調査結果をリアルタイムのトラフィックやセキュリティシグナルと組み合わせて、影響を受けたルートがアクティブかどうか、または不審なトラフィックを受信しているかを評価し、顧客によるレビュー対象として緩和策やパッチを提案しているということです[5][6]。

迅速に発見することができても、影響を受けたソフトウェアを特定し、修正をテストし、是正措置を完了するという作業は、依然として防御者が行わなければなりません。PHPの事例は、特に脆弱なランタイムが他の製品に組み込まれている場合に、このギャップが問題となることを明確に示しています。

アタックサーフェスとしての企業AIエージェント

DarktraceSignal Labsは、攻撃者がすでに環境へのアクセス権を取得した後、信頼されたAIエージェントがどのように悪用される可能性があるかについても調査しました。ダークトレースの研究者は管理されたシミュレーション環境において、侵害後のシナリオとして、Claudeプラットフォームのメモリストア機能が悪用され、外部オペレーターと内部のClaude Codeエージェント間にライブC2チャネルを確立できることを実証しました。外部オペレーターは、このC2チャネルを介して、ネットワーク探索、認証情報へのアクセス、データの持ち出しといったタスクをエージェントに動的に割り当てることができました。エージェントのアクティビティの検知は、エージェントハーネスプロセスからのプロセス作成とネットワークトラフィックの相関付け、および予期された動作からの逸脱を特定するためのビヘイビア分析に基づいて行われました。ダークトレースはこのメモリストアを使ったC2テクニックを実際の攻撃で観測したとは主張していません[7]。

日本で観測されたAI支援による攻撃

日本で観測された証拠は、研究用環境を超えて、実際の脆弱性探索と攻撃にAIが使用されていることを示しています。10月21日、JPCERT/CCは最近の日本国内の組織に対する不正アクセスインシデントについての調査結果を発表しました。JPCERT/CCは攻撃者がAIを使って既知の脆弱性をスキャンしAPIを通じて攻撃を実行していることを確認したと報告しています。JPCERT/CCによると、攻撃インフラを調査した結果、Androidアプリケーションの分析、APIの探索、サーバーサイドリクエストフォージェリを含む脆弱性テストの痕跡が確認され、また、この攻撃インフラは日本国外のユーザー向けサービスも標的としていました[8]。

JPCERT/CCはこの公開資料の中ではARTEXを特定していません。ARTEXに対するアトリビューションは、Microsoft社によるStorm-0940の分析を含む、別の調査に基づいています。

攻撃オペレーションにおけるAI

Microsoft社は、ARTEXを限定的な人間の介入でアクティビティを自動化できる、オープンソースのマルチエージェント型ペネトレーションテストシステムと説明しています。Microsoft社は、2021年から活動している中国政府と連携した攻撃者と評価しているStorm-0940が、数百の組織に対してARTEXを使用したと報告し、ConnectWiseのサプライチェーン侵害がStorm-0940によるものであるとしました[9]。

Microsoft社は、ARTEXがスキャン、偵察、パスワードスプレー、OAuthアプリケーションの悪用を加速させていることを確認しました。ARTEXに駆動されたいくつかの攻撃オペレーションは、最初の標的設定から3時間未満で特権クラウドアクセスに到達しました。ConnectWiseの侵害後、Storm-0940は最大で毎分2,900回の頻度で、2,250を超えるテナントへの認証を試みました[9]。

ダークトレースの脅威調査チームは、後にこのキャンペーンとの関連が判明したインフラに関するアクティビティを、Darktraceテレメトリー内で発見しました。10月13日、Darktraceは、Microsoftが後にConnectWiseの顧客環境でサインインおよびMicrosoft Graphのアクティビティを実行していたと特定したアドレスの1つである144.172.64[.]128に関連する認証アクティビティの失敗を記録しました。Darktraceの分析では、約20分間に65回の認証失敗が確認されました。

図1:2026年10月13日、144.172.64[.]128が関与した認証失敗イベントを示すDarktrace Advanced Searchの結果(顧客を特定できる情報は削除済み)。

Darktraceのテレメトリーは、後にこのキャンペーンとの関連が確認されたインフラから、認証の失敗が繰り返し発生していたことを明らかにしています。これはARTEXの実行や侵害の成功を立証するものではありません。観測時点では、Microsoft社による後のアトリビューションについての情報はありませんでした。つまり、アナリストが把握していたのは振る舞いそのものでした。短時間に同一の送信元から認証に繰り返し失敗したということ、および関連するアイデンティティ、アプリケーション、ネットワークティビティについてのデータです。

Microsoft社は、10月10日から14日にかけて、8組織の327アカウントを対象とした、より広範なパスワードスプレー攻撃を報告しました。151,000件を超えるログオン失敗が記録され、なかでも11月10日には111,000件を超えていましたが、このキャンペーンによる認証成功、トークン発行、Graph呼び出し、ディレクトリ変更はいずれもありませんでした。また、Microsoftは、Storm-0940による標的化の大半が成功しなかったとも報告しています[9]。

攻撃者が認証を突破したケースでは、Microsoft社はサービスプリンシパルによるサインインに続いて、Graphおよびディレクトリ操作が行われたことを確認しました。アクティビティには、偵察、アプリケーション認証情報の変更、権限の変更を試みる行為が含まれていました。Microsoft社はサービスプリンシパルによるサインインとGraphアクティビティ、ディレクトリ変更およびリソースアクセスを相関づけることを推奨しています[9]。

アトリビューションの前に振る舞い

PHPとARTEXの事例は、異なる情報から始まっています。PHPの防御担当者は、どのソフトウェアに緊急の対策が必要かを把握していたものの、当初はエクスプロイトついての情報が限られていました。それでも、プロセスの実行、ファイルの変更、外部への通信は、侵害の証拠となったでしょう。

PHPとARTEXの観測結果は、量と影響範囲の違いも示しています。DarktraceはPHPの脆弱性公開時期に広範なスキャンを観測しました。一方ARTEX関連のインフラでは認証アクティビティが集中して発生していました。どちらの観察結果も、それ単独では侵害を実証するものではなく、いずれのケースにおいても、最初のやり取りに続く振る舞いを調べることが調査上の手がかりとなります。

DarktraceのARTEX関連の検知は、認証関連の振る舞いから始まりました。Microsoft社が攻撃インフラのアトリビューションを公表したのはその8日後でした。アトリビューションはコンテキストを提供するものではありましたが、環境内で最初に記録された事象を変更するものではありませんでした。

AIは今や攻撃サイクルの複数のポイントに存在しています。Daybreakは脆弱性の発見と修正にモデルを適用しています。Darktrace Signal Labsは信頼される企業内AIエージェントがどのように悪用されうるかを、管理された環境内で実証しました。JPCERT/CCは最近のインシデントにおけるAI支援による脆弱性探索およびAPI攻撃を確認しました。Microsoft社は実際の攻撃でStorm-0940がARTEXを使用していることを報告しました [4][7][8][9]。

Microsoft社の研究結果はまた、攻撃の規模と影響は別に評価しなければならないことも示しています。ARTEXを使った1つのキャンペーンは151,000回以上のログオン失敗を生成し、アクセスに至らなかったものの、他のキャンペーンでは3時間未満で特権クラウドアクセスに到達した例もありました。セキュリティチームは大量の試行アクティビティと、認証を突破し権限の変更やリソースアクセスへと進むものを区別しなければなりません。

これらのケースを評価するのに必要な証拠は、これまでに良く知られているものです。つまり認証記録、プロセス実行、アプリケーションやディレクトリの変更、ファイルアクティビティやネットワーク通信です。AIはこれらの振る舞いの発生頻度を増大させます。防御者はこのような状況下でもそれらのシーケンスと影響を判断しなければならないのです。

担当:Emma Foulger、Sam Lister、Dylan Evans、Moishe Tajtelbaum

参考資料

[1] NCSC-NL, php2shell vulnerabilities (CVE-2026-109618, CVE-2026-109619), 21 October 2026. https://github.com/NCSC-NL/php2shell

[2] Imperva, https://www.imperva.com/blog/node2shell-from-brotli-data-to-remote-code-execution/

[3] Cyber Security Agency of Singapore, https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-151/

[4] OpenAI, Daybreak: Tools for securing every organization in the world, 22 June 2026. https://openai.com/index/daybreak-securing-the-world/

[5] OpenAI Developers, Scaling cyber defenders with Daybreak, 21 August 2026. https://developers.openai.com/blog/scaling-cyber-defenders-with-daybreak

[6] OpenAI, Cloudflare links vulnerability discovery to defense with OpenAI, 21 October 2026. https://openai.com/index/cloudflare-cyber/

[7] Darktrace Signal Labs, Shared Memories as a Covert C2 Channel, draft research supplied for review.

[8] JPCERT/CC, Recent AI-Assisted Cyber Attacks in Japan: Investigating Attack Infrastructure and Techniques, 21 October 2026. https://blogs.jpcert.or.jp/en/2026/10/web_api_attacks.html

[9] Microsoft Security Research and Microsoft Threat Intelligence, AI-driven, large-scale nation-state campaign using ARTEX enables supply chain compromise, 21 October 2026. https://www.microsoft.com/en-us/security/blog/2026/10/21/storm-0940-uses-artex-agentic-ai-connectwise-supply-chain-compromise/

[10] Darktrace, Advancing the Use of Frontier AI in Cybersecurity: Darktrace Joins the OpenAI Daybreak Cyber Partner Program to Explore Defensive AI Integrations, 22 June 2026. https://www.darktrace.com/blog/advancing-the-use-of-frontier-ai-in-cybersecurity-darktrace-joins-the-openai-daybreak-cyber-partner-program-to-explore-defensive-ai-integrations

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

Blog

/

OT

/

October 23, 2026

Beyond the Fridge: Exposed Industrial Control Systems

Default blog imageDefault blog image

Introduction

In October 2026, hundreds of supermarkets across France were reportedly affected by a cyberattack targeting their refrigeration systems. According to public reports, the attackers gained access to internet-connected controllers and modified their settings, forcing refrigeration units into high and extremely low temperatures and causing significant disruption. Total losses have been reported to reach several million euros.

The incident drew attention to the security of industrial refrigeration systems, particularly older devices with exposed management interfaces and known vulnerabilities.

The exact details of how the attackers gained access have not been confirmed, however it is speculated that the public-facing web server could be accessed with the username “admin” and password being the current date. Researchers from Claroty’s Team82 identified a vulnerability in Danfoss AK-SM 8xxA Series in 2025, “CVE-2025-41450", allowing for administrative access using a time-based “code-of-the-day" for authentication [1].

Default credentials, outdated firmware and publicly accessible administrative interfaces have been an issue for years. And yet these systems continue to appear in internet scans and require little sophistication to gain admin access. A simple search of internet-connected devices shows a range of exposed devices from Programmable Logic Controllers (PLCs) and remote gateways, to, yes, more fridges.

Darktrace malware researchers identified hundreds of IoT and OT devices publicly exposed on the internet, many of which are configured with no authentication, weak credentials, or default credentials. As shown in Figure 1, an exposed Copeland XWEB web interface, used to manage Dixell equipment, including refrigerators, can provide the ability to remotely control connected devices.

‍

Figure 1: Copeland XWEB interface used to control systems including refrigerators and air conditioning.

However, it’s not only fridges; web management interfaces for industrial controls are also publicly accessible, often protected only by weak credentials. Figure 2 shows an example of a publicly exposed WAGO interface. The WAGO management interface is a configuration and administration panel for controllers. Through it, a logged-in user can view device details and diagnostics, manage user accounts and passwords, update firmware, back up or restore the full configuration, set the clock, and manage SD card storage. While it typically doesn’t manage switch outputs or read live process values, someone with access could still disrupt operation by changing network or Modbus settings, loading bad firmware or configurations, or by resetting passwords and enabling insecure services.

‍

Figure 2: WAGO Management interface.

‍

The issue extends beyond management interfaces. During our research, we identified publicly accessible web interfaces belonging to PLCs, including Rockwell Automation Allen-Bradley devices. In each case, the risk arises from how the devices have been deployed and configured, not from a flaw in the vendors’ products.

‍

Figure 3: Web interface for Allen-Bradley CompactLogix controller.

‍

Figure 3 shows the web interface of an Allen-Bradley CompactLogix controller. Unlike the previous examples, this interface provides a view into the controller's operation, including running tasks, network connections, memory usage and diagnostic information. Rockwell Automation's CompactLogix controllers are commonly used to automate industrial processes, from manufacturing and packaging lines to water treatment and material handling systems. Depending on their configuration, these controllers can operate motors, pumps, valves and other physical equipment.

Although in this example the interface shown does not provide direct control over the PLC's logic, it exposes information about the model, firmware, network layout, and connections, which is useful reconnaissance for a bigger attack.

The concern is not necessarily that every exposed interface allows an attacker to immediately manipulate industrial processes. However, these devices are accessible from the public internet in the first place, providing information about systems that may be responsible for controlling physical equipment.

The attacks on refrigeration systems in France highlight the consequences of poorly secured industrial devices. As demonstrated throughout this research, publicly accessible management interfaces are not limited to refrigeration controllers but extend to PLCs and other systems used to manage industrial equipment.

Finding these devices requires little effort. Internet scanners make it possible to identify publicly exposed interfaces quickly, and in some cases these interfaces rely on publicly documented default credentials or have no authentication at all. As attackers increasingly use AI tools, such attacks may be identified and carried out faster and at a greater scale.

The consequences of this access depend on the device and the functionality exposed. While some interfaces provide little more than diagnostic information, others allow users to modify configurations, disrupt communications, or change settings that affect physical equipment. In industrial environments, this can result in operational downtime, damaged equipment and financial losses.

Weak passwords, default credentials and exposed administrative interfaces are not new security issues. Yet their continued presence on internet-connected industrial systems demonstrates how easily preventable weaknesses can leave physical operations vulnerable to attack.

Exposed devices often come from third-party suppliers and contractors, who frequently install refrigeration controllers, gateways and PLCs without the organization ever being aware they are connected to the internet. Asset visibility remains an important foundation, but organizations should assume that some unknown assets and services will exist. Effective security therefore also depends on continuous monitoring, anomaly detection, network segmentation and rapid response, so that risky exposure and unusual activity can be identified and addressed before it becomes disruptive.

Darktrace helps security teams gain visibility across IT and OT and respond to risks: https://www.darktrace.com/products/operational-technology.

Copeland, Dixell, WAGO, Rockwell Automation, Allen-Bradley and CompactLogix are trademarks of their respective owners. Their use here is for identification only and does not imply any affiliation with or endorsement by those owners.

References

1.        https://claroty.com/team82/research/freeze-the-controller-defrost-the-food-uncovering-vulnerabilities-in-danfoss-refrigeration-controllers

‍

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