Summary
Short Summary: Latvian intelligence apprehended a Russian agent spying on military installations, revealing detailed information was passed to Russia.
Extended Summary: On August 27, 2025, the Latvian State Security Service captured a Russian agent engaged in espionage targeting Latvia's military facilities. The man conveyed critical data about locations, layouts, and security setups of various installations, including construction activities and training of Latvian and NATO forces. Procedures were conducted at multiple sites near Riga, enabling seizure and analysis of relevant materials. This espionage effort jeopardizes not only Latvia's safety but also that of other Baltic states by potentially facilitating Russian hostile intelligence operations. The detainee remains in custody pending further investigation, underscoring the ongoing threat posed by Russian covert actions in the Baltic region.
Description and Notes
The Latvian State Security Service arrested a Russian agent on August 27, 2025, for spying on military facilities within Latvia. The suspect passed detailed intelligence to Russian intelligence services about the location, layouts, security systems, construction of new military sites, Latvian troop training, and NATO troop presence across military installations. Investigations included searches at four locations around Riga, with ongoing examination of seized data carriers and documents. The detainee is held in custody as a preventive measure, and the disclosed information also posed threats to the security interests of Latvia and other Baltic countries.
Evidence
Location
Countries: Latvia Unknown
Location: Riga and its surroundings
Follow-up / Investigation
| Country | Status | Link | Notes |
|---|---|---|---|
| Latvia | Investigation | — | — |
Processed Payload
Raw Payload
Review & Decision
Event History
| Timestamp | Actor | Action | Change |
|---|---|---|---|
| 2025-11-28 04:37 UTC | 127.0.0.1 | re_enrich_queued |
Status: processed → pending
|
| 2025-11-28 04:33 UTC | 127.0.0.1 | re_enrich_queued |
Status: processed → pending
|
| 2025-11-28 04:31 UTC | 127.0.0.1 | re_enrich_queued |
Status: processed → pending
|
| 2025-11-28 04:27 UTC | 127.0.0.1 | re_enrich_queued |
Status: processed → pending
|
| 2025-11-28 04:20 UTC | 127.0.0.1 | retry |
Status: processed → pending
|
| 2025-11-28 03:57 UTC | 127.0.0.1 | re_enrich_queued |
Status: processed → pending
|
| 2025-11-28 00:23 UTC | 127.0.0.1 | retry |
Status: error → pending
|
| 2025-11-26 13:24 UTC | 127.0.0.1 | re_enrich_queued |
Status: approved → pending
|
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.