HMI default credentials → operations disruption
Wonderware / iFix HMI exposed to the corporate network with vendor-default credentials. Operators see attacker-controlled values + commands sent to PLCs through legit channels.
§ Context
Assumed environment: foothold inside corporate IT. HMI server reachable from there. Credentials never rotated from vendor defaults / shared across sites.
§ Steps
- 01Issue commands via legit UIInitial AccessT1078— Valid Accounts
- 02Identify HMI server (Wonderware / iFix / Ignition)DiscoveryN-NMAP-INTERNAL— Internal Nmap Sweep
- 03Send dangerous setpoints to PLCsImpactOT-MODBUS-WRITE— Modbus TCP Write to PLC
- 04Vendor-default admin credentialsInitial AccessOT-HMI-DEFAULTS— HMI Default Credentials
- 05Suppress alarms / falsify operator viewImpactOT-SAFETY-OVERRIDE— Safety Instrumented System Override
§ References
- T1078Valid Accounts
§ Frequently asked
- What is the "HMI default credentials → operations disruption" attack path?
- Wonderware / iFix HMI exposed to the corporate network with vendor-default credentials. Operators see attacker-controlled values + commands sent to PLCs through legit channels. It chains 5 steps drawn from real-world offensive-security techniques.
- What starting position does this attack require?
- The first step is Issue commands via legit UI (T1078) — a initial access primitive. Assumed environment: foothold inside corporate IT.
- What is the final impact of this kill-chain?
- The final step lands on Suppress alarms / falsify operator view (OT-SAFETY-OVERRIDE), which falls under Impact. From here, an operator typically pivots into post-exploitation or maintains persistence.
- How can defenders detect or prevent this attack?
- Detection and prevention vary per step. Refer to each linked MITRE ATT&CK entry under "References" — every technique on that page lists defensive controls, detection telemetry, and known threat-actor usage.
§ Related dossiers
- Shared techniques2
Industroyer2 IEC-104 substation hijack
Timed payload speaks IEC-60870-5-104 to substation RTUs at attacker-chosen hour; sends 'open breaker' commands across a substation, blackouts a grid section.
- Shared techniques2
z/OS TN3270 → RACF userID brute → mainframe shell
Internet-/intranet-exposed TN3270 mainframe terminal. Userids follow predictable HR scheme. Brute-force passwords; many environments allow short / dictionary passwords for legacy reasons.
- Shared techniques2
Reconfigure MFP LDAP → harvest service-account credentials
Walk up to / network-into the MFP admin web panel (default creds), change the LDAP address-book server to attacker IP — printer immediately re-binds and sends its service-account creds in cleartext.
- Shared techniques2
Open MQTT broker → smart-estate takeover
Shodan-indexed MQTT broker on TCP/1883 with no auth. Subscribe to '#' to harvest every device topic; publish to relays/locks/lights/thermostats.
- Shared techniques2
Engineering workstation → push payload to PLC
Compromise the OT engineer's laptop (corporate-network adjacent, jumphost-reachable). Use legit engineering tools (TIA Portal / Studio 5000) to download attacker ladder logic to the PLC.
- Shared techniques2
Reachable Modbus PLC → direct register override
Modbus has no authentication. From a foothold on a reachable OT network, write to coils / holding registers directly with pymodbus.