Bellingcat and its investigative partners have established that Russian politician, Vladimir Kara Murza, was followed by a specialist FSB team prior to his suspected poisonings in 2015 and 2017.

Members of the same FSB team, some of whom have medical and chemical weapons backgrounds, tailed Alexey Navalny before he was poisoned with a Novichok substance in August 2020.
Kara-Murza is a well-known Russian politician, film-maker and an outspoken critic of Russian president Vladimir Putin. The circumstances around his suspected poisonings have long remained a mystery.
Travel details of FSB team members show they followed Kara-Murza on a campaign trip outside Moscow that ended less than 48 hours before his first poisoning incident in May 2015.
Kara-Murza recovered in the US before returning to Russia. Yet the same team began tailing him again just five months after he came back. He was poisoned for the second time in February 2017.
The number of coinciding trips – seven destinations with fourteen overlapping flights or journeys – renders a coincidental overlap between the travels of Kara-Murza and FSB squad members statistically implausible.
On at least one tailing operation, FSB squad members were accompanied by a senior official from the FSB’s 2nd Service, better known as the “Directorate for Protection of the Constitution and the Fight against Terorism”.
This officer, Roman Mezentsev, has previously traveled on joint bookings with high-level Kremlin officials including Vladislav Surkov, President Putin’s former advisor, who is long thought to have played a powerful role in Kremlin politics
Mezentsev is the highest ranking FSB officer whom we have identified on any tailing trip linked to an FSB poisoning operation.
Phone and flight records show Mezentsev frequently interacted and traveled with the chief of the directorate of the 2nd Service, Alexey Zhalo, and with other high-ranking FSB and government officials.
Mezentsev’s recent phone records also show that he communicated with scientist Col. Makshakov, the deputy chief of the FSB’s Criminalistics Institute and de facto chief of the FSB’s poisoning program.
Another potentially relevant finding in this report is that we have tracked the earliest incident of Kara-Murza being tailed to just a few days before the assassinaiton of Boris Nemtsov near the Kremlin.
This temporal overlap, paired with the similarity in risk profile of the two political activists, raises renewed questions about whether the Russian security services may have known or had a role in Nemtsov’s assassination
It must be noted, however, that the death of Nemtsov (he was murdered in a shooting) does not appear to follow the known methods of the poison squad.
Although, the FSB has been behind shooting assassinations before, such as the murder of Zelimkhan Khangoshvili in 2019 https://t.co/qxxHAGG777
Kara-Murza, like Nemtsov, played a crucial role in the lobbying for and implementation of the Magnitsky Act which allows the US government to freeze assets of Rusisian and other government officials deemed to be human rights offenders
This legislation was sponsored in the US Congress by John McCain and has been a thorn in the side of the Russian leadership
Kara-Murza described to us in great detail the symptoms he felt upon becoming ill in 2015 and 2017. These included difficulty breathing, heavy perspiration, a starkly accelerated pulse and uncontrollable bouts of vomiting.
When he was poisoned for a second time in 2017, Kara-Murza’s wife secured samples of his blood and, on her return to the United States, handed them to US toxicology laboratories for analysis

More from World

Good question: what proofs has BDA provided of his authenticity?

Let's go through some of them.


- BDA predicted the Saudis would assassinate Suleimani. They did.
- He said the dog that got Badghadi's arm deserved a Medal Of Honor. The next day the President posted a joke image showing him giving the dog a MoH.

- He said one of his ops in Syria would severely disrupt a CIA drug trafficking operation. This was proved true within a few days:
https://t.co/Hranupwcxj
- He sent gold to Brazil to help pay for an anti-trafficking operation there. That op became public soon afterwards.

- On May 31 this year, he predicted the President would be giving a speech the next day. June 1, the President gives a surprise address at the Rose Garden.
- He predicted the US would be making diplomatic moves on Greenland. True.

- He said the US would be pulling all troops out of Afghanistan. This was confirmed within the month.
- He claimed earthquakes would be hitting Iran's nuclear facilities in December. Yep.
- There were FOUR facilities hit, not the three made public. Also true.
In 2016,Turkey arrested Abdulkadir Yapcan, a prominent Uighur political activist living in the country since 2001 and initiated his extradition. In 2017, Turkey and China signed an agreement allowing extradition even if the purported offense is only illegal in 1of the 2️⃣countries


Since early 2019, Turkey has arrested hundreds of Uighurs and sent them to deportation centers. And Erdogan’s remarks have turned diplomatically bland, just like any Uighur-related coverage in newspapers controlled by Erdogan and his supporters.

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.