CTIPilot

Siemens SIMATIC S7-300

product · product:siemens-simatic-s7-300 single-source-national-cert

Coverage timeline
2
first 2026-08-09 → last 2026-08-20
Peak priority
high
2 high
Sources cited
4
3 hosts
Sections touched
2
active-threats, deep-dive
Co-occurring entities
8
see Co-occurring entities below
ATT&CK techniques
14
pinned v19.2 · see below

Hunting pivots

Releases covered
Siemens SIMATIC S7-300 ×2
ATT&CK techniques
T1046 ×2T1021.004T1036T1070T1078T1078.001T1133T1190T1531T1561.002T1572T1587.004T1588.007T1596.005
Tags
default-config ×2ot-ics ×2ai-abusenation-statevulnerabilities

ATT&CK techniques

14 techniques observed across 2 entries, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Reconnaissance TA0043

T1596.005Search Open Technical Databases: Scan Databases×1

Adversaries may search within public scan databases for information about victims that can be used during targeting. Various online services continuously publish the results of Internet scans/surveys, often harvesting information such as active IP addresses, hostnames, open ports, certificates, and even server banners.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · ATT&CK page ↗

Resource Development TA0042

T1587.004Develop Capabilities: Exploits×1

Adversaries may develop exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than finding/modifying exploits from online or purchasing them from exploit vendors, an adversary may develop their own exploits. Adversaries may use information acquired via Vulnerabilities to focus exploit development efforts. As part of the exploit development process, adversaries may uncover exploitable vulnerabilities through methods such as fuzzing and patch analysis.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · ATT&CK page ↗

T1588.007Obtain Capabilities: Artificial Intelligence×1

Adversaries may obtain access to generative artificial intelligence tools, such as large language models (LLMs), to aid various techniques during targeting. These tools may be used to inform, bolster, and enable a variety of malicious tasks, including conducting Reconnaissance, creating basic scripts, assisting social engineering, and even developing payloads.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · ATT&CK page ↗

Initial Access TA0001

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · ATT&CK page ↗

Persistence TA0003

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Privilege Escalation TA0004

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Stealth TA0005

T1036Masquerading×1

Adversaries may attempt to manipulate features of their artifacts to make them appear legitimate or benign to users and/or security tools. Masquerading occurs when the name or location of an object, legitimate or malicious, is manipulated or abused for the sake of evading defenses and observation. This may include manipulating file metadata, tricking users into misidentifying the file type, and giving legitimate task or service names.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · ATT&CK page ↗

T1070Indicator Removal×1

Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity. Rather than broadly removing evidence, adversaries may target specific artifacts that appear anomalous or are likely to draw scrutiny, while leaving sufficient data intact to maintain the appearance of normal system behavior.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1078Valid Accounts×1

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access, network devices, and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1078.001Valid Accounts: Default Accounts×1

Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS, the root user account in ESXi, and the default service account in Kubernetes.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Discovery TA0007

T1046Network Service Discovery×2

Adversaries may attempt to get a listing of services running on remote hosts and local network infrastructure devices, including those that may be vulnerable to remote software exploitation. Common methods to acquire this information include port, vulnerability, and/or wordlist scans using tools that are brought onto a system.

Evidence: 2026-08-20/joint-advisory-active-threat-siemens-s7-plcs · 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Lateral Movement TA0008

T1021.004Remote Services: SSH×1

Adversaries may use Valid Accounts to log into remote machines using Secure Shell (SSH). The adversary may then perform actions as the logged-on user.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Command and Control TA0011

T1572Protocol Tunneling×1

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Impact TA0040

T1531Account Access Removal×1

Adversaries may interrupt availability of system and network resources by inhibiting access to accounts utilized by legitimate users. Accounts may be deleted, locked, or manipulated (ex: changed credentials, revoked permissions for SaaS platforms such as Sharepoint) to remove access to accounts. Adversaries may also subsequently log off and/or perform a System Shutdown/Reboot to set malicious changes into place.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

T1561.002Disk Wipe: Disk Structure Wipe×1

Adversaries may corrupt or wipe the disk data structures on a hard drive necessary to boot a system; targeting specific critical systems or in large numbers in a network to interrupt availability to system and network resources.

Evidence: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · ATT&CK page ↗

Story timeline

  1. 2026-08-20Five US agencies warn of an active threat to Siemens S7 PLCs, AI-written Python tooling built on the standard S7 libraries, dressed as legitimate OT monitoring software
    active-threatsThe agencies say the targeting is not limited to Siemens, and that what they see is reconnaissance rather than confirmed manipulation
  2. 2026-08-09CERT Polska: a second Polish CHP plant was shut down on 29 December 2025 through the distribution operator's private APN, the first real-world use of that path into an OT network
    deep-diveA mobile-carrier private APN, shared by a wind farm and a heat plant, carried an attacker from a substation firewall to the turbine controls

Where this entity is cited

  • deep-dive1
  • active-threats1

Source distribution

  • cert.pl2 (50%)
  • bleepingcomputer.com1 (25%)
  • ic3.gov1 (25%)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

All cited sources (4)

Entries about Siemens SIMATIC S7-300 (2)

2026-08-20 · view entry permalink →

HIGHupdatedNATOB2

Five US agencies warn of an active threat to Siemens S7 PLCs, AI-written Python tooling built on the standard S7 libraries, dressed as legitimate OT monitoring software

The NSA, CISA, the FBI, the Department of Energy and the Environmental Protection Agency published a joint advisory on 2026-08-19 stating that "This advisory relates to an active threat to Siemens S7 Series programmable logic controllers (PLCs)," and adding a scope caveat that matters more than the headline: "However, ongoing PLC targeting activity is broader than Siemens PLCs. All PLC owners and operators should apply relevant mitigations to reduce the risk to their devices and systems" (BleepingComputer, 2026-08-19). The actively targeted devices are the S7-200, S7-300, S7-400, S7-1200 and S7-1500. The sectors the agencies name as most targeted are critical manufacturing, energy, water and wastewater systems, chemical, food and agriculture, and commercial facilities, and they note S7 controllers are also used in the defence industrial base.

The access path described involves no novel vulnerability. Actors find exposed controllers through internet-scanning services (Censys and ZoomEye are named) and then attack critical and high-severity vulnerabilities, outdated software and weak authentication (BleepingComputer, 2026-08-19). What is new is the tooling and how it presents itself: the advisory reports attackers using artificial intelligence to develop Python exploitation scripts built on the snap7.dll and python-snap7 libraries (the standard open-source means of speaking S7comm to a Siemens controller) and disguising those custom tools as legitimate OT monitoring software. Those tools can provide read and write access to PLC memory, configuration data and ladder-logic programs over S7comm, and the advisory's own behaviour mapping lists conducting read and write operations on data blocks among the actor activity it describes. That combination is the uncomfortable part for a defender: the protocol traffic is the protocol working as designed, the library is the one an integrator would legitimately use, and the process name claims to be a monitoring product.

The agencies' own characterisation of intent is careful and worth carrying precisely: the activity appears focused on persistent reconnaissance, potentially preparing attackers for disruption to critical infrastructure, including data theft, equipment damage, extended downtime or safety incidents (BleepingComputer, 2026-08-19). That is a statement about preparation, not about control-system manipulation having occurred, and an entry that blurred the two would misrepresent what five agencies were willing to say. The recommended actions are correspondingly unglamorous: inventory S7 controllers, install the latest security updates, block internet access to them, strengthen access controls, and monitor for unusual activity targeting these devices.

This advisory relates to an active threat to Siemens S7 Series programmable logic controllers (PLCs),

However, ongoing PLC targeting activity is broader than Siemens PLCs. All PLC owners and operators should apply relevant mitigations to reduce the risk to their devices and systems.

BleepingComputer, quoting the joint advisory

Identify any systems directly or indirectly accessible from untrusted networks

against backup gold copy

NSA, CISA, FBI, Department of Energy and Environmental Protection Agency, joint cybersecurity advisory (FBI mirror)
Updaterun 2026-08-21T0410Z-intelactionsevidencereferencessectorstechniquesbody

The earlier entry recorded the five agencies' warning, the targeted controller families, the AI-developed Python tooling built on the standard S7 libraries, and the assessment that the activity is focused on persistent reconnaissance potentially preparing for disruption. It was composed single-source from an outlet's reading of the advisory, because the advisory publishes as a PDF only and the agency's own page refuses every transport available here, and nothing in this environment could turn PDF bytes into text. That capability was added this run, so the primary has now been read. What follows is only what the earlier entry could not carry.

The advisory's scope note comes first, because it changes who should act. Its opening note states this advisory relates to an active threat to Siemens S7 Series programmable logic controllers, and then widens the frame: ongoing PLC targeting activity is broader than Siemens PLCs, all PLC owners and operators should apply relevant mitigations to reduce risk to their devices and systems, and the Siemens-specific content should be understood and applied as one subset of the wider threat landscape. An operator running a different vendor's controllers is inside the advisory's intended audience, not outside it.

Five named detection classes. The agencies direct defenders to hunt for anomalies across five specific axes, and each is a behaviour rather than an indicator:

  • Anomalous S7comm behaviour: connections from non-engineering workstations, unusual data block access patterns, and write operations outside change windows. The first of those three is the most valuable and the cheapest to implement, because the set of hosts that legitimately speak S7comm to a controller is small, known, and rarely changes.
  • Reconnaissance indicators: sequential IP scanning on port 102, repeated connection attempts with varying parameters, and enumeration of CPU properties.
  • Tool artefacts: use of the Snap7 library outside approved engineering workstations, Python scripts with S7comm functionality, and unauthorised monitoring-software installations. This is the detection counterpart to the tooling the earlier entry described: the same libraries that make the attacker's scripts work are the ones whose presence on an unexpected host is the signal.
  • Temporal anomalies: S7comm activity out of hours, connection patterns consistent with automated scripting rather than human operators, and configuration changes with no corresponding work order or change ticket.
  • Geographic anomalies: connections from countries or address ranges not associated with vendors or integrators.

The hardening sequence, in the order the agencies put it. First, an immediate inventory of all Siemens S7 Series PLCs: verify current firmware on every S7-200, S7-300, S7-400, S7-1200 and S7-1500 controller against a backup gold copy, identify any system directly or indirectly accessible from untrusted networks, and map all engineering workstations with TIA Portal, STEP 7 or S7 programming access. Second, patch as soon as possible, prioritising internet-facing or DMZ-resident controllers, bringing TIA Portal and STEP 7 to current versions, consulting Siemens ProductCERT advisories for known vulnerabilities and their workarounds, and testing every update in a development environment before production. Beyond that the advisory calls for ensuring PLCs are not reachable from the internet, strengthening access controls, monitoring for unauthorised activity, and hardening PLC services, including setting write protection and read/write protection levels on the devices themselves.

The instruction that is easiest to overlook is aimed at the supply chain: entities that rely on systems integrators or third-party managed service providers should share the advisory with those parties and request implementation of the mitigations. For a public-sector operator whose OT estate is maintained under contract, that is the action item, because none of the hardening above happens without the integrator doing it.

Triage: the discriminator running through all five detection classes is which host is speaking, when, and with what tooling, not the S7comm protocol itself, which is exactly what an engineering workstation is supposed to use. A programming session from an approved workstation inside a change window, matching a work order, is normal; the same protocol from a host with no engineering role, or outside a change window, or without a corresponding ticket, is the signal. The gold-copy firmware comparison is the one check that speaks to whether something has already happened rather than whether it is happening now.

Builds on: 2026-08-09/cert-polska-private-apn-pivot-into-ot-chp-plant-shutdown · 2026-08-13/cve-2026-58115-simatic-iot2050-node-red-unauth-root

threat20 Aug 06:48Zsingle-source · national CERTOpen finding ↗
Sources: NSA, CISA, FBI, Department of Energy and Environmental Protection Agency (joint advisory) · BleepingComputer

2026-08-09 · view entry permalink →

HIGHNATOA2

CERT Polska: a second Polish CHP plant was shut down on 29 December 2025 through the distribution operator's private APN, the first real-world use of that path into an OT network

CERT Polska published a follow-up analysis on 2026-08-08 of the coordinated 29 December 2025 attacks on Poland's energy sector, adding a victim its January report did not carry: a smaller combined heat and power plant supplying heat to roughly 50,000 residents, whose industrial control systems came under attack at about 07:00 that morning (CERT Polska, 2026-08-08). The analysis took more than three months, which is why the case was held back from the initial report published on 30 January 2026 (CERT Polska, 2026-08-08). The head of CERT Polska, Marcin Dudek, presented the case at DEF CON in parallel with publication (CERT Polska, 2026-08-08). The report carries no actor attribution.

The finding that generalises beyond Poland is the access path. Substations that connect renewable generation to the distribution grid commonly carry cellular routers whose SIM cards sit in a private APN, a carrier-operated private mobile network the distribution system operator uses to reach the remote terminal unit at each site, in this case over DNP3.0 (CERT Polska, 2026-08-08). The operator's requirements covered the serial path to the RTU but said nothing about the router's own administrative interface, so the Teltonika RUTX50 at the compromised wind farm sat with its serial link to the RTU on one interface and an Ethernet link into a VLAN behind the already-compromised central firewall on the other (CERT Polska, 2026-08-08). CERT Polska states this is the first instance it knows of in which a private APN was the route into an OT network, made possible by a configuration that let arbitrary devices inside the APN talk to one another, a configuration its surveys found common in Poland and which it believes is widely deployed in other countries (CERT Polska, 2026-08-08).

The chain ran as follows. Every compromised wind-farm substation in the original wave (more than 30 grid connection points) used a FortiGate as both VPN concentrator and firewall, with the VPN interface reachable from the internet and accepting accounts defined on the device itself without multi-factor authentication; the attacker held administrative privileges on the device and likely used them to obtain a VPN account with reach across all network segments (CERT Polska, 2026-08-08). From inside, the attacker logged into the Teltonika router over SSH repeatedly during December 2025 and tunnelled from it into the private APN; how the router password was obtained could not be determined, and whether a flaw in the device was used is likewise unresolved (CERT Polska, 2026-08-08). From 18 December the attacker scanned the APN for VNC and HTTP services and for the S7 and Modbus industrial protocols, and found a WAGO PFC200 controller exposing a web administration interface on its WAN side, reachable from the APN and still on the default credentials for the admin account; SSH was not enabled on that interface by default, and the sequence in the carrier's logs indicates the attacker enabled it through the web interface before tunnelling onward into the heat plant's OT network, to which the controller had connectivity for both the SCADA systems and the segments holding process-control devices (CERT Polska, 2026-08-08).

Reconnaissance inside the plant ran from 18 to 25 December. Repeated attempts to reach the firewall's LAN-side web interface using the account names admin, user and a username belonging to the company that deploys telecontrol systems at renewable sites all failed, and were retried three days later without success (CERT Polska, 2026-08-08). On Sunday 21 December, eight days before the attack, the attacker scanned for S7 on 102/TCP, Modbus on 502/TCP, CODESYS on 11740/TCP and RTSP on 554/TCP alongside RDP, VNC and web services, and in one subnet the scan began at the address of the SCADA system itself, which CERT Polska reads as evidence of earlier reconnaissance having already identified the high-value targets (CERT Polska, 2026-08-08). On Christmas Day the attacker established successful S7 connections to three Siemens PLCs, most plausibly to prepare the destructive step (CERT Polska, 2026-08-08).

On 29 December activity inside the plant network ran from about 05:30 to about 10:10, meaning the operator's recovery work beginning around 07:30 started while the attacker was still present (CERT Polska, 2026-08-08). The first action after tunnelling through the WAGO controller was to open the SCADA server's web interface, then reach an S7-300 over the S7 protocol, repeating the sequence against an S7-1200 and an S7-1500 (CERT Polska, 2026-08-08). According to statements from plant personnel the PLCs were switched to STOP mode and protected with a password blocking both operating-state changes and control-logic modification, shutting down the steam turbine and the process-water treatment system and interrupting cogeneration; prompt operator response held it to a short outage with no interruption to customer heat or electricity supply (CERT Polska, 2026-08-08). The attacker also reconfigured seven Moxa serial device servers and three Moxa switches (factory reset, password changed, addresses moved to unreachable values such as 127.0.0.1) and the timing of the HTTP requests supports a high-confidence assessment that this was automated (CERT Polska, 2026-08-08). Connections to two ABB ACS variable frequency drives were observed with no determinable effect, and attempts against Schneider Electric ATV 6xx drives failed because the attacker targeted 80/TCP while those interfaces listened elsewhere (CERT Polska, 2026-08-08).

Two recovery lessons sit in the anti-forensics. The attacker corrupted the partition table of the WAGO controller used as the gateway, and the operator's own factory reset did not repair it, leaving the device unbootable and its logs unrecoverable; the Teltonika router was factory-reset about thirty minutes after the last plant activity and its address set to 127.0.0.1, and the FortiGate was factory-reset last of all, destroying the logs from the initial entry point (CERT Polska, 2026-08-08). The investigation only recovered router evidence because RutOS versions before 7.07 keep the event database through a factory reset (CERT Polska, 2026-08-08). On the plant side, restoring the Siemens controllers to factory settings and reloading logic backups shortened the outage but deleted the controllers' own logs, and Siemens ProductCERT confirmed they could not be recovered (CERT Polska, 2026-08-08).

Triage: an engineering contractor doing legitimate remote maintenance also logs into a cellular router and reaches PLCs over S7, so neither event alone separates the two. The discriminators here are direction and sequence, the session enters from the APN side of a device whose administrative interface was never meant to face it, port scanning precedes the PLC access by days, and the run-state change is followed within minutes by configuration writes to unrelated serial servers and switches. This plant's operators initially read the shutdown as contractor error during scheduled maintenance and reported it for information only; CERT Polska opened an investigation anyway because it knew of similar events, which is what turned an unexplained failure into a confirmed intrusion (CERT Polska, 2026-08-08).

To the best of our knowledge, the use of a private APN to gain access to the OT network was the first instance of this attack vector being observed in a real-world cyberattack.

The attack was made possible, among other factors, by a misconfiguration that allowed arbitrary devices within the private APN network to communicate with one another.

Surveys conducted among organizations using similar solutions indicated that this configuration was commonly encountered in Poland.

CERT Polska (NASK) 2026-08-08
incident09 Aug 04:42Zsingle-source · national CERTOpen finding ↗
Sources: CERT Polska (NASK)