Delta Electronics DTN Soft arbitrary code execution flaw
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Deserialization vulnerability in Delta DTN Soft allows arbitrary code execution via malicious project files; patch available.
Delta Electronics DTN Soft versions 2.1.0 and prior contain a deserialization of untrusted data vulnerability (CVE-2025-53416) that allows an attacker to execute arbitrary code by crafting a malicious project file and tricking a user into opening it. The vulnerability requires local access and user interaction but carries a CVSS v4 score of 8.4, reflecting high impact on confidentiality, integrity and availability. The flaw affects critical infrastructure operators worldwide, particularly in manufacturing. Delta has released DTN Soft v2.1.0 and DTM Soft v1.6.0.0 (March 25, 2025) as patches; affected organizations should update immediately. CISA reports no known public exploitation of this vulnerability as of the advisory date. The attack vector is local, not remote, and relies on social engineering to deliver a malicious file to an authorized user.
Mentioned in this report
Detection guidance
Delta DTN Soft Spawning Shell or Script Interpreter
DTN Soft launching a command shell, script host or LOLBin child process, consistent with code execution after opening a malicious project file (CVE-2025-53416 deserialization). Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Delta DTN Soft Spawning Shell or Script Interpreter
description: Detects a DTN Soft process (Delta Electronics) spawning a command shell,
script host or common LOLBin. This is the expected post-exploitation pattern when
a crafted project file triggers unsafe deserialization (CVE-2025-53416) and runs
attacker code in the context of the application. The parent match is on the product
name fragment, so tune it to the executable name in your environment.
tags:
- attack.execution
- attack.t1203
- attack.initial-access
- attack.t1566.001
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|contains: DTNSoft
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \rundll32.exe
- \regsvr32.exe
- \certutil.exe
- \bitsadmin.exe
- \msiexec.exe
condition: selection_parent and selection_child
falsepositives:
- DTN Soft installer or updater launching msiexec or cmd for legitimate setup tasks
- Engineers running vendor-provided helper scripts from within the application
level: medium
id: 58a9e339-c634-56fb-b3dd-8fbfa687487a
status: experimental
author: Vorant
references:
- https://www.cisa.gov/news-events/ics-advisories/icsa-25-210-03
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-210-03
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,853 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs