Description and Notes
Between June 13th and 15th, 2025, a significant surge in GNSS spoofing activity was detected across the Baltic Sea and extended into the Kattegat region near Denmark. This disruption affected maritime navigation, causing ships to report erratic AIS positions with errors up to 2.5 km from their true location. Authorities issued multiple advisories to mariners. Distinct spoofing systems, likely operating from Russian naval vessels, were observed transmitting spoofed GNSS signals limited by line-of-sight range (~20-30 nautical miles). The spoofing manifested in characteristic AIS patterns called 'TOREC' triangles, involving hopping spoofed position nodes with scripted sub-patterns, indicating use of commercial off-the-shelf GNSS spoofers such as the Crown JS1-7. The spoofing zones intermittently shift positions, with multiple systems operating simultaneously at sea level. This represents a concerning escalation of electronic warfare tactics extending beyond the Baltic Sea into key navigational chokepoints like the Kattegat and Øresund Strait.
Notes: This event reveals a sophisticated and escalating use of GNSS spoofing as a maritime electronic warfare tool, impacting both navigation and situational awareness in strategically vital waterways around the Baltic and Nordic regions. The use of commercial-off-the-shelf spoofers adapted for naval deployment suggests a scalable tactical measure possibly intended to disrupt NATO and allied maritime operations. Continued monitoring of AIS data, geofencing of spoofing nodes, and cross-verification with aviation GNSS disturbance reports is recommended to track operational patterns and attribution. The extension of spoofing beyond the Baltic Sea into the Kattegat is especially critical, given the area's importance for maritime traffic into the Baltic.
Evidence
Location
Location: Baltic Sea and Kattegat near Denmark
Follow-up / Investigation
| Country | Status | Link | Notes |
|---|---|---|---|
| Denmark | Investigation | — | — |
| Russia | Official Statement | — | — |
Processed Payload
Raw Payload
Review & Decision
Payload History
Re-enrichment
Re-enrich
Enrichment-only: keeps existing processed data, screenshots, and media. Re-runs only the enrichment step (AI extraction) without refetching the source or regenerating screenshots. Use this if enrichment failed or you need updated AI-extracted data.
Destructive Actions
Reprocess
Full rebuild: discards processed data, refetches source, regenerates screenshots/media, and re-enriches. Reset to pending and rerun the full pipeline from the raw payload. This will discard the current processed data, refetch the source, regenerate screenshots/media, and re-enrich from scratch. Use this if processing failed or you need a full rebuild.
Delete Event
⚠️ Warning: This permanently removes the event and its history. This action cannot be undone.