Blog
/
Email
/
May 1, 2026

Comment les attaques par injection de prompt transmises par email peuvent cibler l’IA d’entreprise – et pourquoi c’est important

L’injection de prompt est une menace émergente qui ne compte pour l’instant qu’une poignée de victimes attestées. Elle cible le mode de traitement des données par les systèmes d’IA plutôt que d’exploiter les vulnérabilités logicielles traditionnelles. À mesure que l’IA agentique s’intègre dans les environnements d’entreprise, les cybercriminels peuvent tenter de manipuler ces systèmes à l’aide de prompts dissimulés au sein du contenu des e-mails du quotidien.
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
Kiri Addison
Senior Director of Product
Default blog image
01
May 2026

Que sont les attaques par injection de prompt transmises par email ?

À mesure que les organisations adoptent rapidement des assistants d’IA pour améliorer leur productivité, une nouvelle catégorie de cyberrisques apparaît : l’injection de prompt par e-mail. Contrairement aux attaques traditionnelles qui ciblent les vulnérabilités logicielles ou reposent sur l’ingénierie sociale, il s’agit d’intégrer des instructions malveillantes ou manipulatrices dans un contenu qu’un système d’IA traitera dans le cadre de son flux de travail normal. Comme les outils d’IA modernes sont conçus pour ingérer de grands volumes de données et raisonner à partir de ceux-ci, notamment des e-mails, des documents et des historiques de conversation, ils peuvent involontairement traiter du texte dissimulé et contrôlé par des attaquants comme un prompt légitime.  

Chez Darktrace, nos analyses ont montré une hausse de 90 % du nombre de déploiements clients présentant des signaux associés à de potentielles tentatives d’injection de prompt depuis que nous avons commencé à surveiller ce type d’activité, fin 2025. Même s’il n’est pas toujours possible d’attribuer chaque cas de manière définitive, les systèmes de notation internes conçus pour identifier les caractéristiques compatibles avec une injection de prompt ont enregistré un nombre croissant de correspondances présentant un niveau de confiance élevé. La tendance à la hausse suggère que les attaquants expérimentent activement ces techniques.

Exemples récents d’attaques par injection de prompt

Parmi les premiers exemples répertoriés de cette menace en pleine évolution, on trouve HashJack et ShadowLeak, qui illustrent concrètement à eux deux ce qu’est l’injection de prompt.

HashJack est une nouvelle technique d’injection de prompt découverte en novembre 2025, qui exploite les navigateurs Web optimisés par l’IA et les assistants de navigation Web agentiques basés sur l’IA. En dissimulant des instructions malveillantes dans le fragment d’URL (après le symbole # ) d’un site Web légitime et digne de confiance, les attaquants peuvent tromper les assistants Web basés sur l’IA et les inciter à effectuer des actions malveillantes, par exemple en insérant des liens de phishing, de fausses coordonnées ou des indications trompeuses directement dans un contenu qui semble être un résultat généré par une IA digne de confiance.

ShadowLeak est une méthode d’injection de prompt permettant d’exfiltrer des données personnelles identifiables, identifiée en septembre 2025. Il s’agissait d’une faille dans ChatGPT (désormais corrigée par OpenAI) qui fonctionnait via un agent connecté aux emails. Les cybercriminels envoyaient à la cible un email contenant un prompt caché amenant l’agent à leur divulguer des informations sensibles sans aucune intervention de l’utilisateur ni accès à son interface.

Quel risque représentent les attaques par injection de prompt transmises par email ?

Les assistants d’IA d’entreprise disposent souvent d’une visibilité complète sur les e-mails, les documents et les plateformes internes. Cela signifie qu’un cyberattaquant n’a pas besoin de compromettre des identifiants ni de se déplacer latéralement dans un environnement. S’ils y parviennent, ils peuvent influencer l’IA afin qu’elle récupère les informations pertinentes de manière transparente, sans avoir à recourir à la compromission et à l’élévation de privilèges.

Le premier risque est l’exfiltration de données. Dans un scénario d’injection de prompt, des instructions malveillantes peuvent être intégrées à un e-mail ordinaire. Comme dans l’attaque ShadowLeak, lorsque l’IA traite ce contenu dans le cadre d’une tâche légitime, elle peut interpréter le texte caché comme une instruction. Cela pourrait amener l’IA à divulguer des données sensibles, à résumer des communications confidentielles ou à révéler un contexte interne dont l’obtention nécessiterait autrement des efforts considérables.

Le deuxième risque est l’empoisonnement des flux de travail agentiques. À mesure que les systèmes d’IA assument des rôles plus actifs, l’injection de prompt peut influencer leur comportement au fil du temps. Un cyberattaquant pourrait intégrer des instructions qui persistent au fil des interactions, incitant par exemple l’IA à inclure des liens malveillants dans ses réponses ou à rediriger les utilisateurs vers des ressources non fiables. De cette manière, le cybercriminel s’insère dans le flux de travail, agissant concrètement comme un intermédiaire (« l‘homme du milieu ») au sein du système d’IA.

Pourquoi les autres solutions ne parviennent-elles pas à détecter les attaques par injection de prompt transmises par e-mail ?

L’injection de prompt remet en question bon nombre des postulats sur lesquels repose la sécurité traditionnelle de la messagerie. Elle ne correspond pas aux schémas habituels du phishing, où l’objectif consiste à inciter un utilisateur à cliquer sur un lien ou à ouvrir une pièce jointe.  

La plupart des solutions de sécurité sont conçues pour détecter les signaux associés à l’engagement des utilisateurs : les liens suspects, les pièces jointes inhabituelles, ou les indices d’ingénierie sociale. L’injection de prompt échappe entièrement à ces indicateurs, ce qui signifie qu’il y a moins de signaux d’alerte évidents.

Dans ce cas, l’intention est en réalité à l’ opposé de la sollicitation de l’utilisateur. L’objectif est simplement que l’email soit distribué et reste dans la boîte de réception, en paraissant inoffensif et banal. Le destinataire n’est pas censé interagir avec l’élément malveillant, ni même le remarquer.

La détection est encore compliquée par la nature même des prompts. Contrairement aux signatures de malware connues ou aux schémas de phishing récurrents, les prompts injectés peuvent varier considérablement dans leur structure et leur formulation. Cela rend peu fiables les approches simples de mise en correspondance de motifs, comme les expressions régulières (regex). Un ensemble de règles trop large risque de générer un grand nombre de faux positifs, tandis qu’un ensemble trop restreint risque de ne pas couvrir la diversité des injections possibles.

Comment Darktrace détecte-t-il ces types d’attaques ?

L’approche de Darktrace en matière de sécurité de la messagerie, plus généralement, consiste à aller au-delà des indicateurs individuels et à évaluer le contexte, ce qui s’applique également ici.  

Par exemple, notre score de densité de prompts identifie les regroupements de formulations semblables à des prompts au sein d’un email, plutôt que de relever de simples occurrences isolées. Au lieu de considérer la présence d’une expression comme un signal de blocage, l’analyse porte sur la présence d’une concentration inhabituelle de ces schémas, susceptible de révéler une injection. Une pondération supplémentaire peut être appliquée en présence de signes d’obfuscation. Par exemple, un texte masqué à l’utilisateur — par exemple en raison d’une police blanche ou d’une taille de police nulle — mais qui reste lisible par les systèmes d’IA peut indiquer une tentative de dissimulation de prompts malveillants.

En effet, des indices comportementaux plus généraux viennent s‘y ajouter. Le même contexte de communication utilisé pour détecter d’autres menaces reste pertinent, comme le fait de déterminer si le contenu est inhabituel pour le destinataire, ou s’il s’écarte des schémas habituels.

Interrogez votre fournisseur de messagerie sur les injections de prompt visant par e-mail

L’injection de prompt ne cible pas seulement les employés, mais aussi les systèmes d’IA sur lesquels ils s’appuient, si bien que les approches de sécurité doivent tenir compte des deux.

Même s’il existe des signes clairs d’un phénomène émergent, il reste à voir quelle popularité l’injection de prompt rencontrera auprès des cyberattaquants à l’avenir. Néanmoins, compte tenu de l’impact potentiel de ce type d’attaque, il vaut la peine de vérifier si ce risque a été pris en compte par votre fournisseur de sécurité de la messagerie.

Questions à poser à votre fournisseur de sécurité de la messagerie

  • Quelles mesures de protection sont en place pour empêcher les e-mails d’influencer les flux de travail pilotés par l’IA au fil du temps ?
  • Comment évaluez-vous le contenu d’un e-mail inoffensif pour un lecteur humain, mais susceptible de comporter des instructions dissimulées destinées aux systèmes d’IA ?
  • Si un email ne contient ni lien, ni pièce jointe, ni indice d’ingénierie sociale, quels signaux votre plateforme utiliserait-elle pour identifier une intention malveillante ?

‍

Consultez le hub produit Darktrace / EMAIL pour découvrir comment nous détectons les menaces avancées ciblant les communications et y répondons.  

En savoir plus sur la sécurisation de l’IA dans votre entreprise.

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
Kiri Addison
Senior Director of Product

More in this series

No items found.

Blog

/

AI

/

November 2, 2026

PHP Vulnerabilities, ARTEX and the Growing Role of AI in Cyber Attacks

Default blog imageDefault blog image

The disclosure of CVE-2026-109618 and CVE-2026-109619 placed immediate pressure on organizations running PHP. Both vulnerabilities can allow unauthenticated remote code execution, including in products and appliances where PHP is embedded, and updates depend on third-party vendors [1].

Early guidance focused on patching internet-facing systems and monitoring for behavior associated with successful exploitation, including unexpected command execution, Webroot changes and outbound connections from PHP servers.

Darktrace observed widespread scanning across monitored environments involving hundreds of distinct source IP addresses that public reporting has associated with activity targeting the PHP vulnerabilities. The volume of scanning was significantly greater than the evidence available for successful exploitation. For analysts, that distinction is important. Scanning demonstrates interest in exposed infrastructure; establishing compromise requires evidence of subsequent behavior on the targeted system, including command execution, file modification or unexpected outbound communication.

PHP is not an isolated example. Imperva subsequently demonstrated remote code execution against a vulnerable Node.js build through malicious Brotli data, reproducing execution through compressed HTTP responses and configured request parsers. The same inputs were rejected by the patched runtime. Imperva linked its Node2Shell and PHP2Shell research to the increasing speed of vulnerability discovery and exploit development. [2]

While Darktrace has not observed direct evidence of CVE-2026-109618 or CVE-2026-109619 exploitation, on October 21st we observed a six-month high in detections consistent with zero-day exploitation activity, representing a 64% increase compared to historic data. This increase has not been confirmed as related to the PHP vulnerabilities. Darktrace’s behavioral approach is designed to detect anomalous activity without relying solely on rules written for a specific exploit. Comparable increases were observed around the Log4j disclosure and other globally significant vulnerability disclosures.

AI-assisted vulnerability research

The PHP disclosure arrives as AI systems have become more capable at vulnerability research [3]. OpenAI launched Daybreak in June 2026, combining GPT-5.5-Cyber, Codex Security and partnerships with security researchers and software maintainers. OpenAI says its models have been applied to discovering and generating patches for vulnerabilities in browsers, network infrastructure, FreeBSD and the Linux kernel. Darktrace joined the OpenAI Daybreak Cyber Partner Program in June to explore how OpenAI's cyber capabilities could be integrated within Darktrace products and services [4][10].

OpenAI reported in August that Codex Security Cloud had analyzed more than 30 million commits across more than 30,000 codebases. According to OpenAI, Cloudflare uses models accessed through Daybreak to investigate customer-authorized code and combines findings with live traffic and security signals to assess whether affected routes are active or receiving suspicious traffic, with proposed mitigations and patches remaining subject to customer review [5][6].

Faster discovery still leaves defenders with the work of locating affected software, testing fixes and completing remediation. The PHP case shows that gap clearly, particularly when vulnerable runtimes are embedded inside other products.

Enterprise agents as an attack surface

Darktrace Signal Labs has also examined how a trusted enterprise agent could be abused after an attacker has already obtained access to an environment. In a controlled simulation, researchers demonstrated that, in that post-compromise scenario, the Claude platform’s memory stores feature could be abused to establish a live C2 channel between an external operator and internal Claude Code agents. The external operator was able to dynamically assign network discovery, credential access, and data exfiltration tasks to the agents via this C2 channel. Detection of the agents’ activities relied on the correlation of process creation and network traffic activity from agent harness processes, alongside behavioral analysis to identify deviations from expected behavior. Darktrace has not claimed it observed this memory-store command-and-control technique in operational attacks [7].

AI-assisted attacks in Japan

Evidence from Japan indicates AI being used for vulnerability scanning and attacks outside controlled research. On 21 October, JPCERT/CC published findings from an investigation into recent unauthorized access incidents affecting organizations in Japan. JPCERT/CC states that it confirmed attackers had used AI to scan for known vulnerabilities and conduct attacks through APIs. According to JPCERT/CC, its examination of attack infrastructure found evidence of Android application analysis, API discovery and testing for weaknesses including server-side request forgery, and the infrastructure also targeted services intended for users outside Japan [8].

JPCERT/CC does not identify ARTEX by name in that publication. The named ARTEX attribution comes from separate investigations, including Microsoft's analysis of Storm-0940.

AI in offensive operations

Microsoft describes ARTEX as an open-source, multi-agent penetration-testing system capable of automating activity with limited human interaction. Microsoft reported that Storm-0940, which it assesses to be a China state-aligned actor active since 2021, used ARTEX against hundreds of organizations, and Microsoft attributed the ConnectWise supply-chain compromise [9].

Microsoft observed ARTEX accelerating scanning, reconnaissance, password spraying and OAuth application abuse. Several ARTEX-driven operations reached privileged cloud access less than three hours after initial targeting. Following the ConnectWise compromise, Storm-0940 attempted to authenticate to more than 2,250 tenants at rates of up to 2,900 attempts per minute [9].

Darktrace Threat Research found activity in its own telemetry involving infrastructure later associated with the campaign. On 13 October, Darktrace recorded failed authentication activity involving 144.172.64[.]128, one of the addresses Microsoft later identified as performing sign-ins and Microsoft Graph activity in ConnectWise customer environments. Darktrace analysis identified 65 failed authentication attempts in around 20 minutes.

Figure 1: Darktrace Advanced Search showing failed authentication events involving 144.172.64[.]128 on 13 October 2026, (customer-identifying information redacted).

The telemetry establishes repeated failed authentication from infrastructure later associated with the campaign. It does not establish ARTEX execution or successful compromise. At the time of observation, Microsoft's later attribution was unavailable. Analysts therefore had the behavior itself: repeated failed authentication from the same source over a short period, together with any related identity, application or network activity inside the environment.

Microsoft documented a wider password-spray campaign against 327 accounts across eight organizations between 10 and 14 October. It recorded more than 151,000 failed logons, including more than 111,000 on 11 October, but no successful authentication, token issuance, Graph call or directory change from that campaign. Microsoft also reported that most Storm-0940 targeting was unsuccessful [9].

Where the actor progressed beyond authentication, Microsoft observed service-principal sign-ins followed by Graph and directory operations. Activity included reconnaissance, application credential changes and attempts to modify privileges. Microsoft recommends correlating service-principal sign-ins with Graph activity, directory changes and resource access [9].

Behavior before attribution

The PHP and ARTEX cases begin with different information. PHP defenders knew which software required urgent remediation but initially had limited information about exploitation. Process execution, file modification and outbound communication could still provide evidence of compromise.

The PHP and ARTEX observations also illustrate the difference between volume and impact. Darktrace observed broad scanning around the PHP disclosure, while the ARTEX-associated infrastructure produced concentrated authentication activity. Neither observation independently demonstrates compromise and in each case examining the behavior that follows the initial interaction is the investigative clue.

The Darktrace ARTEX-related observation began with authentication behavior. Microsoft publicly attributed the source infrastructure eight days later. That attribution added context, but it did not change what had originally been recorded in the environment.

AI is now present at several points in this cycle. Daybreak applies models to vulnerability discovery and remediation. Darktrace Signal Labs demonstrated how a trusted enterprise agent could be co-opted in a controlled environment. JPCERT/CC confirmed AI-assisted vulnerability scanning and API attacks in recent incidents. Microsoft documented ARTEX being used by Storm-0940 in active operations [4][7][8][9].

Microsoft's findings also show why scale and impact must be assessed separately. One ARTEX-associated campaign produced more than 151,000 failed logons without successful access, while other operations reached privileged cloud access in less than three hours. Security teams have to distinguish high-volume attempts from activity that progresses through authentication, privilege changes and resource access.

The evidence required to assess these cases remains familiar: authentication records, process execution, application and directory changes, file activity and network communication. AI can increase the rate at which those behaviors occur. Defenders still need to establish their sequence and impact.

Credit to Emma Foulger, Sam Lister, Dylan Evans, Moishe Tajtelbaum

References

[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

/

November 2, 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
Your data. Our AI.
Elevate your network security with Darktrace AI