detecting-stuxnet-style-attacks

Detects Stuxnet-style cyber-physical attacks via PLC logic integrity monitoring and physics-based anomaly detection.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill detecting-stuxnet-style-attacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detecting-stuxnet-style-attacks
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/ot-ics-security/detecting-stuxnet-style-attacks
Command: npx skills add https://github.com/xalgord/xalgorix --skill detecting-stuxnet-style-attacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sophisticated attacks on industrial control systems can modify PLC logic while spoofing sensor readings, making manipulation invisible to operators and conventional network monitoring. This Skill provides detection methods for these Stuxnet-style cyber-physical attacks across the full attack chain.

Core Features & Use Cases

  • PLC Logic Integrity Monitoring: Compares running PLC program blocks (OB, FC, FB, DB) against known-good baselines to detect injected, removed, or modified logic.
  • Physics-Based Anomaly Detection: Cross-validates independent measurements such as VFD frequency vs RPM, power vs speed, and vibration signatures to expose spoofed sensor values.
  • Attack Chain Coverage: Maps detection points across USB-borne initial access, lateral movement, engineering workstation compromise, PLC logic modification, and process manipulation using MITRE ATT&CK for ICS techniques.
  • Use Case: A security team protecting a critical infrastructure facility uses the integrity monitor to flag a new unauthorized function block in a Siemens PLC, then confirms process manipulation when power consumption contradicts the reported RPM.

Quick Start

Ask the AI to build a PLC logic integrity baseline comparison and physics-based anomaly detection plan for your Siemens S7 environment following the Stuxnet attack chain.

Frequently Asked Questions about detecting-stuxnet-style-attacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect unauthorized PLC logic modifications?

Compare the running PLC program against a known-good offline baseline by checking block count, block sizes, and per-block checksums for OB, FC, FB, and DB blocks. New blocks, removed blocks, or checksum mismatches indicate potential logic injection mapped to MITRE technique T0833.

How does physics-based anomaly detection catch sensor spoofing?

Physics-based detection cross-validates independent measurements so spoofed values contradict physical laws. For example, motor RPM must match VFD frequency, and power consumption scales with RPM cubed, so a frozen RPM reading diverges from actual power draw.

Why is network monitoring alone insufficient for Stuxnet-style attacks?

Injected logic blocks only traverse the network during the initial S7comm or CIP download; afterward only the physical process reveals manipulation. Detection requires periodic PLC logic integrity comparison and physics-based process models rather than passive network sensors.

What indicators reveal engineering workstation compromise in OT environments?

Key indicators include modified DLLs such as s7otbxdx.dll in Siemens STEP 7 installations, unsigned binaries executing from removable media, unexpected USB device connections, and unauthorized modifications to PLC project files. EDR with OT awareness and file integrity monitoring detect these host artifacts.

When should I not use this Stuxnet-style detection approach?

Do not use it for basic OT intrusion detection, malware reverse engineering of Stuxnet samples, or PLC programming tasks. It targets advanced APT-style threats against high-value OT environments and requires existing baselines, physics models, and monitoring infrastructure.