First reportedAugust 3, 2010
ActivityActivity date not specified
Last updatedFeb 2, 2026, 12:00 AM UTC
Record confidencemed

Key facts

Affected

  • Industrial organizations operating Siemens Step7/WinCC engineering environments
  • Organizations operating industrial control systems (ICS) targeted by Stuxnet (including Iran’s nuclear program, per U.S. government analysis)

Initial access

  • unknown

Impact

  • service_disruption
  • unknown

Attribution

unknown low confidence

Public and governmental analyses discuss suspected state sponsorship, but definitive attribution is not formally confirmed in the cited primary advisories.

CVEs and ATT&CK

No CVE or ATT&CK association is captured in this curated record.

Mitigations

Now

  • Apply vendor guidance for ICS hardening (engineering workstations and PLC networks)Reduces exposure of high-risk ICS components and aligns controls with known ICS threat patterns highlighted in advisories.

Soon

  • Segment ICS networks and strictly control connectivity between corporate IT and OTLimits malware movement into engineering environments and reduces blast radius if a Windows host is compromised.

Later

  • Restrict removable media and implement allowlisting on engineering workstationsReduces common malware propagation paths in ICS environments and limits execution of unauthorized binaries.

Detection ideas

Monitor for unauthorized changes to engineering workstation project files and PLC logic

Alert on unexpected modifications to Step7 project files, PLC download events outside maintenance windows, or abnormal PLC command sequences.

Data sources: ICS engineering workstation logs, Configuration management, OT network telemetry

Detect anomalous binaries and driver installs on ICS engineering workstations

Flag new unsigned/suspicious drivers, unusual DLL injection into engineering tools, or new binaries appearing in system directories on OT workstations.

Data sources: EDR telemetry, Windows Security Event Logs, File integrity monitoring

Sources