66.132.172.102

Summary (Bottom Line Up Front)

External threat actor 66.132.172.102 conducted targeted reconnaissance against industrial control systems using Modbus protocol attacks between March 20-26, 2026, with 79 recorded events. This HIGH confidence threat demonstrates sophisticated capabilities targeting critical infrastructure with potential for operational disruption. Immediate hardening of ICS/SCADA networks and enhanced monitoring of Modbus communications is recommended.

HTTP TCP TCP/SYN TLS TLS/1.0 TLS/1.2+ auto
Activity Timeline
INITIAL REPORT2026-03-26T19:05:06Z
Source: Analyst Manual Entry
External threat actor 66.132.172.102 conducted targeted reconnaissance against industrial control systems using Modbus protocol attacks between March 20-26, 2026, with 79 recorded events. This HIGH confidence threat demonstrates sophisticated capabilities targeting critical infrastructure with potential for operational disruption. Immediate hardening of ICS/SCADA networks and enhanced monitoring of Modbus communications is recommended.
Technical details
Attack Vector: Multi-protocol reconnaissance campaign utilizing HTTP, TCP, TLS 1.0/1.2+ protocols targeting industrial systems
Primary Techniques: MITRE T1046 (Network Service Scanning) with focus on Modbus protocol exploitation
Attack Patterns: Modbus broadcast attacks, Function Code 43 device identification requests, and unauthenticated write attempts
Volume: 79 events across 6-day period (March 20 22:00 - March 26 02:00 UTC) targeting 3 unique destination ports
Key IOCs: Source IP 66.132.172.102, Modbus Function Code 0x2B device enumeration, hex payload pattern 5a4700000005002b0e0100
Assessment: AI-detected attack patterns suggest advanced threat actor with specialized ICS targeting capabilities and potential state-sponsored attribution
IOCs
IP:66.132.172.102
Recommendations
  • Implement network segmentation to isolate ICS/SCADA systems from corporate networks and internet-facing infrastructure
  • Deploy protocol-aware monitoring solutions capable of detecting anomalous Modbus traffic and unauthorized function code usage
  • Block source IP 66.132.172.102 at perimeter firewalls and add to threat intelligence feeds for ongoing monitoring
  • Conduct immediate audit of Modbus-enabled devices for default credentials, unnecessary network exposure, and authentication bypass vulnerabilities
  • Establish baseline behavioral profiles for legitimate Modbus communications to improve detection of reconnaissance activities