Strikes on Yandex: Establishing the Link to Anti-Israel Bot Networks

Did Ukrainian strikes on Yandex data centres disrupt anti-Israel bot networks? Asaf Eli Cohen Safiev examines what network traffic and activity on X can tell us, and what evidence would link specific accounts to the servers that were hit.

Strikes on Yandex: Establishing the Link to Anti-Israel Bot Networks

By Asaf Eli Cohen Safiev

Last week, Moscow rejected Netanyahu’s remarks about antisemitic bot networks. According to Ynet, the prime minister also said that anti-Israel activity and calls to "Free Palestine" fell by 60% following Ukrainian strikes on Yandex data centers. The report provided no methodology. For Israel, the question matters: did the strikes disrupt hostile information infrastructure, or were different indicators combined into one persuasive explanation?

 Between 7 and 11 October, Ukraine attacked three Yandex data centers, following Russian strikes on Ukrainian internet infrastructure. Services were disrupted. On 26 October, Yandex said its three supercomputers were undamaged and had been relocated. Attacks on computing infrastructure have strategic significance regardless of bots: data processing, services and digital resilience depend on it.

  Yandex’s record warrants scrutiny. The removal of political information from its services and filtering of information about the war in Ukraine are documented. Its role in Russia’s information system requires examination, not unquestioning acceptance of its explanations. But the use of its infrastructure and its involvement in organising a campaign are distinct questions. Each requires evidence.

Claims that bot networks had been disabled spread on X. A user posted an X Radar chart apparently showing falling mentions of "Free Palestine" and "genocide", alongside rising mentions of "Zelensky". Zelensky said there were fewer bots and less hatred. His office subsequently told BBC Verify that he meant the atmosphere online, not a measured reduction in bot activity.

Three questions must be separated: what happened to the servers, what changed in posts, and who controlled the accounts. Timing alone does not establish an operational connection.