4,361 STS Transfer Alerts in 45 Days. Zero Acknowledged. Ship-to-Ship Transfer Is Now the Dominant Behavioral Motif.

The Setup

4,361 ship-to-ship transfer motif alerts fired in the 45 days ending June 2, 2026. Not a single one was acknowledged. The same is true for the 2,062 AIS_manipulation_dark alerts and 641 AIS_manipulation_spoof alerts that round out the high-severity stack. Of 7,065 total high-severity behavioral motifs detected in the window, zero carry an adjudication.

The headline from the May 5 analysis framed AIS manipulation as the dominant alert type. That framing no longer holds. Ship-to-ship transfer events now represent 61.7% of the alert stack — 4,361 of 7,065. AIS manipulation (dark and spoof combined) accounts for 38.3%.

The Chain

The ship_to_ship_transfer motif fires when position history, speed profile, and proximity events match the signature of an offshore cargo transfer: vessels slowing, holding station in close proximity, then resuming course. Confidence is 1.00 for all 4,361 STS alerts. Robustness score is 1.00 across the full population. There are no partial-confidence events in this category.

Weekly breakdown over the 45-day window:

| Week of | STS Alerts | |---------|-----------| | Apr 13 | 761 | | Apr 20 | 451 | | Apr 27 | 602 | | May 4 | 97 | | May 11 | 646 | | May 18 | 611 | | May 25 | 894 | | Jun 1 | 299 (partial) |

The week of May 25 produced 894 alerts — the highest single week in the window and 66% above the rolling average of 539 per week. The May 4 trough (97 events) may reflect a detection gap rather than a true lull; it is an outlier in an otherwise 450–760 range.

For scale: the total high-severity motif stack grew from 4,578 (as of the May 5 analysis) to 7,065 over approximately four weeks — a 54% increase. STS transfer volume grew from roughly 2,655 to 4,361 — 64% growth, outpacing the broader stack. AIS manipulation (dark + spoof) grew from roughly 1,923 to 2,703 — 40% growth. STS transfers accelerated faster than manipulation.

The Implication

A 100%-confidence, 100%-robustness alert with zero acknowledgment after 45 days is not a noise problem. Noise gets suppressed. The suppression workflow is available: suppression_window_hours, suppression_until, and suppressed_repeat_count columns are all populated in the schema. The suppressed_repeat_count for this population is zero across all 4,361 events. These are not deduped repeats accumulating unseen — they are distinct behavioral matches firing and going unread.

STS transfers are not inherently sanctionable. But they are inherently significant: cargo that moves vessel-to-vessel offshore does not log through port systems. It produces no Bill of Lading in port records, no harbor dues timestamp, no consignment manifest at the terminal. The cargo exists in transit; its identity and declared destination depend entirely on what the receiving vessel self-reports in AIS.

When STS transfer activity spikes 66% in a single week, and no analyst has opened the queue in 45 days, the compliance exposure is structural. Any downstream screening that relies on port-logged manifest data for these vessels will have a gap, and the scale of that gap is growing faster than the AIS manipulation signal.

What to Watch

Weekly STS transfer volume. The May 25 spike (894) is the benchmark. Two consecutive weeks above 800 would indicate that the June 1 partial-week data (299) is truncated, not a regression. Two consecutive weeks below 500 would indicate the spike was event-specific.

The AIS_manipulation:STS_transfer ratio is a structural indicator worth tracking monthly. In April the split was roughly 58:42 in favor of STS. It is now 62:38. A continued shift toward STS transfer dominance signals that offline cargo rerouting is growing faster than identity obfuscation as the primary evasion vector.

Limitations

Motif detection does not physically locate or verify the vessels. The ship_to_ship_transfer motif fires on behavioral signature — proximity, speed match, dwell, resumption — without satellite or SAR verification. A vessel pair that matches the pattern without actually transferring cargo cannot be distinguished from one that did. No subtype taxonomy exists for this motif; all 4,361 alerts carry identical confidence and robustness values regardless of cargo type or geographic context.

Zero acknowledgments could reflect analyst workload, triage prioritization of other alert categories, or an absence of a staffed adjudication workflow for this queue. What happens downstream of this table is not observable in this dataset.

Data as of 2026-06-02. Source: Overwatch motif_alerts, 45-day window. Total high-severity alerts: 7,065 across ship_to_ship_transfer (4,361), AIS_manipulation_dark (2,062), AIS_manipulation_spoof (641), and fraudulent_documentation (1).