Blog
/
/
February 11, 2021

Detecting IoT Threats in Control Systems

Discover how Darktrace uncovers pre-existing threats in Industrial IoT systems. Learn about advanced detection techniques in industrial control systems.
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
David Masson
VP, Field CISO
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
11
Feb 2021

Industrial IoT (IIoT) devices are a pressing concern for security teams. Companies invest large sums of money to keep cyber-criminals out of industrial systems, but what happens when the hacker is already inside? Gateways and legacy security tools generally sit at the border of an organization and are designed to stop external threats, but are less effective once the threat is already inside. During this period, cyber-criminals carry out further reconnaissance, tamper with PLC settings, and subtly disrupt the production process.

Darktrace recently detected a series of pre-existing infections in Industrial IoT (IIoT) devices at a manufacturing firm in the EMEA region. The organization already had Darktrace in place in one area of the environment, but after seeing how the AI could successfully detect zero-day vulnerabilities and threats, they expanded the deployment, allowing Darktrace to actively monitor and defend interactions among its 5,000 devices, and dramatically improving visibility.

An unknown emerging threat was identified by Darktrace / OT omultiple machines within hours of Darktrace being active in the environment. By casting light on this previously unknown threat, Darktrace enabled the customer to perform full incident response and threat investigation, before the attacker was able to cause any serious damage to the company.

Though it is unclear how long the devices had been infected, it is likely to have been first introduced manually via an infected USB. The affected endpoints were being used as part of a continuous production process and could not be installed with endpoint protection.

Darktrace / OT; however, easily detects infections across the digital estate, regardless of the type of environment or technology. Darktrace AI does not rely on signature-based methods but instead continuously updates its understanding of what constitutes ‘normal’ in an industrial environment. This self-learning approach allows the AI to contain zero-days that have never been seen before in the wild, as well as detecting the new appearance of pre-existing attacks.

Industrial IoT attacked

Only a few hours after Darktrace AI had begun defending the wider connections and interactions across the manufacturing firm, Darktrace detected a highly unusual network scan. A timeline of events, from first scan to full incident response results and conclusions, is shown below:

Figure 1: Timeline of incident response across 28 hours

Darktrace’s AI recognized that the device was exploiting an SMBv1 protocol in order to attempt lateral movement. In addition to anonymous SMBv1 authentication, Darktrace detected the device abusing default vendor credentials for device enumeration.

The device made a large number of unusual connections, including connections to internal endpoints which the company had previously been unaware of. As these occurred, the Threat Visualizer, Darktrace’s user interface, provided a graphical visualization of the incident, illuminating the unusual activity’s spread from the infected device across the infrastructure in question.

Figure 2: The Darktrace Threat Visualizer

Darktrace identified that the infected Industrial IoT device was making an unusually large number of internal connections, suggesting an effort to perform reconnaissance.

Darktrace’s Cyber AI Analyst launched an immediate investigation into the alert, surfacing an incident summary at machine speed with all the information the security team needed to act.

Figure 3: An example of an AI Analyst Report on a network scan

The Cyber AI Analyst further identified two other devices behaving in a similar way, and these were removed from the network by the customer in response. When investigated by the security team, these devices were shown to be infected with the Yalove and Renocide worms, and the Autoit trojan-dropper. Open source intelligence suggests these infections are often spread via removable media such as USB drives.

Using Darktrace’s Advanced Search function, the customer was able to investigate related model breaches to build a list of similar indicators of compromise (IoCs), including failed external connections to www.whatismyip[.]com and DYNDNS IP addresses on HTTP port 80.

Recurring infections: How to deal with a persistent attack

In total, Darktrace was used to identify 13 infected production devices. The customer contacted the equipment owner, whose response confirmed that they had seen similar attacks on other networks in the past, including recurring infections.

Recurring infections imply one of two things: either, that the malware has a persistence mechanism, where it uses a range of techniques to remain undetected on the exploited machine and achieve persistent access to the system. Alternatively, a recurring infection could mean that the IoT manufacturer was not able to find all infected devices when they were first alerted to the compromise, and thus did not shut down the attack in its entirety.

As the infected machines are owned by a third party, they could not be immediately remediated. Darktrace AI, however, contained this threat with minimal business disruption. The customer was able to leave the infected devices active, which were still needed for production, confident that Darktrace would alert them if the infection spread or changed in behavior.

Industrial IoT: Shining a light on pre-existing threats

The mass adoption of Industrial IoT devices has made industrial environments more complex and more vulnerable than ever. This blog demonstrates the prevalent threat that attackers are already on the inside, and the importance for security teams to expand visibility over their full industrial system. In this case, the customer was able to use Darktrace’s AI to illuminate a previous blind spot and contain a persistent attack, while minimizing disruption to operations. Crucially, this ‘unknown known’ threat was detected without any prior knowledge of the devices, their supplier, or patch history, and without using malware signatures or IoCs.

The customer was made aware of the infection via the Darktrace SOC service. Yet the same outcome could have been obtained with other workflows provided by Darktrace, such as email alerting, notifications through the Darktrace mobile app, seamlessly integrating Darktrace with a SIEM solution, or alerting via an internal SOC.

Cyber AI Analyst enabled the customer to perform immediate incident response. While waiting for a reinstallation date with the equipment owner, the customer could keep the production devices online, knowing Darktrace would be monitoring the outstanding risk. In an industrial setting, trade-offs like this are often necessary to sustain production. Darktrace helps organizations maintain the vigilance they need to do this securely, and when remediation does become possible, Darktrace can be used to reliably locate the full extent of the infection.

Thanks to Darktrace analyst Oakley Cox for his insights on the above threat find.

Darktrace model detections:

  • Device / Suspicious Network Scan Activity [Enhanced Monitoring]
  • Device / ICMP Address Scan
  • ICS / Anomalous IT to ICS Connection
  • Anomalous Connection / SMB Enumeration
  • Device / Network Scan

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
David Masson
VP, Field CISO

More in this series

No items found.

Blog

/

Cloud

/

January 13, 2026

Runtime Is Where Cloud Security Really Counts: The Importance of Detection, Forensics and Real-Time Architecture Awareness

runtime, cloud security, cnaapDefault blog imageDefault blog image

Introduction: Shifting focus from prevention to runtime

Cloud security has spent the last decade focused on prevention; tightening configurations, scanning for vulnerabilities, and enforcing best practices through Cloud Native Application Protection Platforms (CNAPP). These capabilities remain essential, but they are not where cloud attacks happen.

Attacks happen at runtime: the dynamic, ephemeral, constantly changing execution layer where applications run, permissions are granted, identities act, and workloads communicate. This is also the layer where defenders traditionally have the least visibility and the least time to respond.

Today’s threat landscape demands a fundamental shift. Reducing cloud risk now requires moving beyond static posture and CNAPP only approaches and embracing realtime behavioral detection across workloads and identities, paired with the ability to automatically preserve forensic evidence. Defenders need a continuous, real-time understanding of what “normal” looks like in their cloud environments, and AI capable of processing massive data streams to surface deviations that signal emerging attacker behavior.

Runtime: The layer where attacks happen

Runtime is the cloud in motion — containers starting and stopping, serverless functions being called, IAM roles being assumed, workloads auto scaling, and data flowing across hundreds of services. It’s also where attackers:

  • Weaponize stolen credentials
  • Escalate privileges
  • Pivot programmatically
  • Deploy malicious compute
  • Manipulate or exfiltrate data

The challenge is complex: runtime evidence is ephemeral. Containers vanish; critical process data disappears in seconds. By the time a human analyst begins investigating, the detail required to understand and respond to the alert, often is already gone. This volatility makes runtime the hardest layer to monitor, and the most important one to secure.

What Darktrace / CLOUD Brings to Runtime Defence

Darktrace / CLOUD is purpose-built for the cloud execution layer. It unifies the capabilities required to detect, contain, and understand attacks as they unfold, not hours or days later. Four elements define its value:

1. Behavioral, real-time detection

The platform learns normal activity across cloud services, identities, workloads, and data flows, then surfaces anomalies that signify real attacker behavior, even when no signature exists.

2. Automated forensic level artifact collection

The moment Darktrace detects a threat, it can automatically capture volatile forensic evidence; disk state, memory, logs, and process context, including from ephemeral resources. This preserves the truth of what happened before workloads terminate and evidence disappears.

3. AI-led investigation

Cyber AI Analyst assembles cloud behaviors into a coherent incident story, correlating identity activity, network flows, and Cloud workload behavior. Analysts no longer need to pivot across dashboards or reconstruct timelines manually.

4. Live architectural awareness

Darktrace continuously maps your cloud environment as it operates; including services, identities, connectivity, and data pathways. This real-time visibility makes anomalies clearer and investigations dramatically faster.

Together, these capabilities form a runtime-first security model.

Why CNAPP alone isn’t enough

CNAPP platforms excel at pre deployment checks all the way down to developer workstations, identifying misconfigurations, concerning permission combinations, vulnerable images, and risky infrastructure choices. But CNAPP’s breadth is also its limitation. CNAPP is about posture. Runtime defense is about behavior.

CNAPP tells you what could go wrong; runtime detection highlights what is going wrong right now.

It cannot preserve ephemeral evidence, correlate active behaviors across domains, or contain unfolding attacks with the precision and speed required during a real incident. Prevention remains essential, but prevention alone cannot stop an attacker who is already operating inside your cloud environment.

Real-world AWS Scenario: Why Runtime Monitoring Wins

A recent incident detected by Darktrace / CLOUD highlights how cloud compromises unfold, and why runtime visibility is non-negotiable. Each step below reflects detections that occur only when monitoring behavior in real time.

1. External Credential Use

Detection: Unusual external source for credential use: An attacker logs into a cloud account from a never-before-seen location, the earliest sign of account takeover.

2. AWS CLI Pivot

Detection: Unusual CLI activity: The attacker switches to programmatic access, issuing commands from a suspicious host to gain automation and stealth.

3. Credential Manipulation

Detection: Rare password reset: They reset or assign new passwords to establish persistence and bypass existing security controls.

4. Cloud Reconnaissance

Detection: Burst of resource discovery: The attacker enumerates buckets, roles, and services to map high value assets and plan next steps.

5. Privilege Escalation

Detection: Anomalous IAM update: Unauthorized policy updates or role changes grant the attacker elevated access or a backdoor.

6. Malicious Compute Deployment

Detection: Unusual EC2/Lambda/ECS creation: The attacker deploys compute resources for mining, lateral movement, or staging further tools.

7. Data Access or Tampering

Detection: Unusual S3 modifications: They alter S3 permissions or objects, often a prelude to data exfiltration or corruption.

Only some of these actions would appear in a posture scan, crucially after the fact.
Every one of these runtime detections is visible only through real-time behavioral monitoring while the attack is in progress.

The future of cloud security Is runtime-first

Cloud defense can no longer revolve solely around prevention. Modern attacks unfold in runtime, across a fast-changing mesh of workloads, services, and — critically — identities. To reduce risk, organizations must be able to detect, understand, and contain malicious activity as it happens, before ephemeral evidence disappears and before attacker's pivot across identity layers.

Darktrace / CLOUD delivers this shift by turning runtime, the most volatile and consequential layer in the cloud, into a fully defensible control point through unified visibility across behavior, workloads, and identities. It does this by providing:

  • Real-time behavior detection across workloads and identity activity
  • Autonomous response actions for rapid containment
  • Automated forensic level artifact preservation the moment events occur
  • AI-driven investigation that separates weak signals from true attacker patterns
  • Live cloud environment insight to understand context and impact instantly

Cloud security must evolve from securing what might go wrong to continuously understanding what is happening; in runtime, across identities, and at the speed attackers operate. Unifying runtime and identity visibility is how defenders regain the advantage.

[related-resource]

Continue reading
About the author
Adam Stevens
Senior Director of Product, Cloud | Darktrace

Blog

/

Network

/

January 12, 2026

Maduro Arrest Used as a Lure to Deliver Backdoor

maduro arrest used as lure to deliver backdoorDefault blog imageDefault blog image

Introduction

Threat actors frequently exploit ongoing world events to trick users into opening and executing malicious files. Darktrace security researchers recently identified a threat group using reports around the arrest of Venezuelan President Nicolàs Maduro on January 3, 2025, as a lure to deliver backdoor malware.

Technical Analysis

While the exact initial access method is unknown, it is likely that a spear-phishing email was sent to victims, containing a zip archive titled “US now deciding what’s next for Venezuela.zip”. This file included an executable named “Maduro to be taken to New York.exe” and a dynamic-link library (DLL), “kugou.dll”.  

The binary “Maduro to be taken to New York.exe” is a legitimate binary (albeit with an expired signature) related to KuGou, a Chinese streaming platform. Its function is to load the DLL “kugou.dll” via DLL search order. In this instance, the expected DLL has been replaced with a malicious one with the same name to load it.  

DLL called with LoadLibraryW.
Figure 1: DLL called with LoadLibraryW.

Once the DLL is executed, a directory is created C:\ProgramData\Technology360NB with the DLL copied into the directory along with the executable, renamed as “DataTechnology.exe”. A registry key is created for persistence in “HKCU\Software\Microsoft\Windows\CurrentVersion\Run\Lite360” to run DataTechnology.exe --DATA on log on.

 Registry key added for persistence.
Figure 2. Registry key added for persistence.
Folder “Technology360NB” created.
Figure 3: Folder “Technology360NB” created.

During execution, a dialog box appears with the caption “Please restart your computer and try again, or contact the original author.”

Message box prompting user to restart.
Figure 4. Message box prompting user to restart.

Prompting the user to restart triggers the malware to run from the registry key with the command --DATA, and if the user doesn't, a forced restart is triggered. Once the system is reset, the malware begins periodic TLS connections to the command-and-control (C2) server 172.81.60[.]97 on port 443. While the encrypted traffic prevents direct inspection of commands or data, the regular beaconing and response traffic strongly imply that the malware has the ability to poll a remote server for instructions, configuration, or tasking.

Conclusion

Threat groups have long used geopolitical issues and other high-profile events to make malicious content appear more credible or urgent. Since the onset of the war in Ukraine, organizations have been repeatedly targeted with spear-phishing emails using subject lines related to the ongoing conflict, including references to prisoners of war [1]. Similarly, the Chinese threat group Mustang Panda frequently uses this tactic to deploy backdoors, using lures related to the Ukrainian war, conventions on Tibet [2], the South China Sea [3], and Taiwan [4].  

The activity described in this blog shares similarities with previous Mustang Panda campaigns, including the use of a current-events archive, a directory created in ProgramData with a legitimate executable used to load a malicious DLL and run registry keys used for persistence. While there is an overlap of tactics, techniques and procedures (TTPs), there is insufficient information available to confidently attribute this activity to a specific threat group. Users should remain vigilant, especially when opening email attachments.

Credit to Tara Gould (Malware Research Lead)
Edited by Ryan Traill (Analyst Content Lead)

Indicators of Compromise (IoCs)

172.81.60[.]97
8f81ce8ca6cdbc7d7eb10f4da5f470c6 - US now deciding what's next for Venezuela.zip
722bcd4b14aac3395f8a073050b9a578 - Maduro to be taken to New York.exe
aea6f6edbbbb0ab0f22568dcb503d731  - kugou.dll

References

[1] https://cert.gov.ua/article/6280422  

[2] https://www.ibm.com/think/x-force/hive0154-mustang-panda-shifts-focus-tibetan-community-deploy-pubload-backdoor

[3] https://www.ibm.com/think/x-force/hive0154-targeting-us-philippines-pakistan-taiwan

[4] https://www.ibm.com/think/x-force/hive0154-targeting-us-philippines-pakistan-taiwan

Continue reading
About the author
Tara Gould
Malware Research Lead
Your data. Our AI.
Elevate your network security with Darktrace AI