FSB Apprehends Russian Citizen Over Krasnodar Terror Plot
According to the agency, the suspect had been acting on orders from Ukrainian intelligence and intended to target areas with large public gatherings.
Authorities allege that the individual was recruited by Ukrainian special services via WhatsApp in February 2025. Since then, he had reportedly been collecting classified military data, including intelligence on the movement of Russia’s Black Sea Fleet.
The FSB stated that the suspect planned to use an improvised explosive device (IED) to attack an administrative building at a regional energy facility.
A criminal investigation has been launched. The detained citizen has admitted guilt and agreed to cooperate with investigators.
In a separate case, the FSB also detained another Russian citizen on Tuesday. This individual is accused of supplying Ukraine with intelligence regarding Sukhumi International Airport in Abkhazia. Shared information allegedly included the airport’s layout, surrounding areas, and schedules of Russian officials—data that could support planning a terrorist attack.
Incidents involving espionage linked to Ukrainian intelligence have become more frequent. On Monday, Russian security forces detained two additional Russian nationals who allegedly attempted sabotage at a defense facility in the Moscow region.
Legal Disclaimer:
MENAFN provides the
information “as is” without warranty of any kind. We do not accept
any responsibility or liability for the accuracy, content, images,
videos, licenses, completeness, legality, or reliability of the information
contained in this article. If you have any complaints or copyright
issues related to this article, kindly contact the provider above.
Legal Disclaimer:
EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.
