MASS autonomy on spoofed seas

Statement (NASA form)

Given that the IMO MASS Code is in force for cargo ships, GNSS/AIS spoofing is an operational fact in several seas, and language models are being wired onto ECDIS, remote-ops, and port automation, there is a possibility of an autonomous or remotely operated ship acting on a confident false fix, a ghost AIS contact, or a prompt that reaches steering resulting in collision, grounding, a blocked strait or port, pollution, and casualties — plus a trade shock if the failure clusters.

Condition

the IMO MASS Code is in force for cargo ships, GNSS/AIS spoofing is an operational fact in several seas, and language models are being wired onto ECDIS, remote-ops, and port automation

Departure

an autonomous or remotely operated ship acting on a confident false fix, a ghost AIS contact, or a prompt that reaches steering

Impact

collision, grounding, a blocked strait or port, pollution, and casualties — plus a trade shock if the failure clusters

Maritime risk used to be weather and fatigue. It is now a trust problem at the data layer. GNSS spoofing is present, green, and believed; AIS rebroadcasts the lie; terminals fuse GNSS with inertial sensors in a way that survives an outage and fails on a lying signal. ClassNK warned in June 2026 that Hormuz-class interference makes MASS decision-making unreliable. The MASS Code, in effect 1 July 2026, is a goal-based framework — not a verified defence against a spoofed fix or an LLM on the bridge OT. Rakuten Maritime / ClassNK’s 8 Sep ‘dark cockpit’ paper is explicit: poorly designed almost-autonomous ships can be very dangerous, and fleet-wide software pushes are a concentration risk.