Summary
- European officials briefed on U.S. intelligence findings report that the failed early-August drone attack on an Antonov cargo plane at Leipzig-Halle Airport emerged from a year in which the Russian army was largely fought to a standstill in Ukraine and negotiations with Washington failed to deliver Russian-favored concessions, with Putin allegedly ordering a stepped-up sabotage campaign against NATO countries.
- Western intelligence officials attribute the operation to the GRU’s Special Tasks Service, formed in 2023 under Col. Gen. Andrey Averyanov, with the attack traced to Col. Denis Smolyaninov, one of Averyanov’s department chiefs, previously sanctioned by the European Union and Britain for directing Russian covert operations in Europe.
- German investigators and Serbian prosecutors have documented a Serbia-based logistics network moving modified drones and military-grade Semtex toward Germany, with German cyberintelligence officials tracing drone communications to servers previously used by the GRU and German investigators identifying Oleg Levushkin, a former Russian military officer, as the ground-logistics coordinator.
- Counter-measures targeting the SSD, named operatives, or the Serbian transit network would degrade operational capacity without addressing the strategic driver; the underlying cause persists until the Ukraine impasse resolves on terms Russia accepts or Moscow abandons its objectives.
European officials briefed on U.S. intelligence findings have characterized the failed early-August drone attack on an Antonov cargo plane at Leipzig-Halle Airport as one of the opening operations in a stepped-up sabotage campaign that the officials said Russian President Vladimir Putin ordered against NATO countries. The cargo plane was used to carry military assistance to Ukraine, and German investigators say Russian military-intelligence agents piloted at least three explosive-packed drones positioned around the airport; one struck the Antonov freighter without detonating, another collided with a different plane, and a third exploded near the airport perimeter, with investigators stating the attack could have caused mayhem and casualties at one of Europe’s most important air-cargo airports had it worked as planned. The reported root cause lies in a year in which Ukrainian forces, with European support, largely fought the Russian army to a standstill on the ground while Kyiv was hitting targets deep inside Russia, and in which negotiations between Moscow and Washington failed to produce the concessions Russia sought.
Strategic impasse as reported driver
The article’s central finding is that the campaign’s escalation is sourced to a strategic stalemate. European officials briefed on the findings said the escalation came as Ukrainian forces, with European support, had largely fought the Russian army to a standstill on the ground over the past year, inflicting heavy losses and preventing significant territorial gains. Kyiv was increasingly hitting targets deep inside Russia, including refineries and warehouses of Russia’s largest e-commerce firm. The officials said there was growing frustration in Moscow because neither the fighting nor negotiations with Washington were getting Ukraine to agree to the concessions Putin wanted. Investigators said the broader campaign sought to position agents, explosives and weapons across Europe to strike targets supporting Ukraine and sow chaos that could strengthen political opposition to military aid for Kyiv.
Thomas Graham, a former senior U.S. official now involved in informal talks with the Kremlin, said, “The Kremlin is disappointed that the talks with the United States have not led to the rapid normalization of relations they had hoped for.” The strategic-impasse characterization is source-attributed rather than publicly documented in Russian government statements; political authorization for the campaign is reported by European officials briefed on U.S. intelligence findings, not by an on-the-record Russian directive. Russia has denied involvement in sabotage operations in Europe, and Putin responded to Berlin’s accusations by asking, “Where is the evidence?”; the Kremlin did not respond to a request for comment.
Institutional architecture: SSD, Averyanov, and Smolyaninov
The reported operation draws on institutional infrastructure consolidated in 2023. Western officials said Russia’s clandestine attacks were being led by a branch of Russian military intelligence, or GRU, known as the Special Tasks Service, or SSD. The SSD was formed in 2023 by merging some of Russia’s most lethal clandestine units under a mandate to wage covert warfare against Europe. It is commanded by Col. Gen. Andrey Averyanov, a veteran of clandestine warfare whose operatives have been linked to assassinations, poisonings and bombings across Europe, according to Western officials.
Western intelligence officials said they had traced the Leipzig attack to Col. Denis Smolyaninov, one of Averyanov’s department chiefs who is under European Union and British sanctions for directing Russian covert operations in Europe. Western intelligence had previously identified Smolyaninov as one of the commanders behind a plot to smuggle incendiary devices into the DHL parcel network; investigators believed that operation was ultimately intended to bring down civilian airliners flying to Britain and North America. The reported Smolyaninov–Leipzig link is organizational rather than directly documented in the substrate; the public account does not fully map the internal reporting lines among the SSD, Smolyaninov and the ground coordinator Levushkin, and supports organizational convergence rather than a fully documented direct chain from Smolyaninov to Levushkin.
Ground operations: Levushkin, the Serbian hub, and technical means
The Leipzig operation involved at least three drones packed with military-grade Semtex explosives and positioned in bushes and beneath trees outside the airport perimeter, investigators said. The drones carried German 5G mobile-phone cards and could be piloted remotely over the internet. German cyberintelligence officials traced their communications to servers previously used by the GRU. Investigators said they had uncovered networks smuggling explosives, drones and weapons into the European Union, along with safe houses and concealed underground caches near airports, arms manufacturers and other potential targets.
German investigators believe the Leipzig operation’s ground logistics were coordinated by Oleg Levushkin, a former Russian military officer recruited by the GRU following a criminal conviction. Levushkin directed several Belarusian operatives who transported explosives across borders, assembled the drones and positioned them for the attack, according to investigators and intelligence officials. The network used Serbia as a logistics hub to move modified drones and explosive devices toward Germany. Military-grade Semtex was smuggled in resealed food cans fitted with detonators, and added steel plates turned the devices into fragmentation bombs designed to scatter deadly shrapnel, investigators said. Serbian prosecutors said authorities arrested seven suspects, including a dual Russian-Serbian citizen, in an organized group that procured and stored explosives and drones before shipping them into European Union countries. Two days before the Leipzig attack, Levushkin and at least one Belarusian accomplice flew from Germany to Serbia and onward to Russia.
A server previously used by the GRU is a technical indicator that, by itself, does not prove GRU personnel controlled the drones at the time of the attack. The reported technical details describe the operation’s control and destructive mechanisms but do not establish why the drone that struck the Antonov aircraft failed to detonate.
Continuation indicators and the NATO response debate
After the failed attack, a Kremlin official serving as a back channel to the German government contacted his counterpart in Berlin and warned that Leipzig would not be the last attack, according to officials familiar with the exchange.
Since the Leipzig attack, European countries have seen a sharp uptick in gray-zone assaults. Arsonists struck drone manufacturers in Estonia and Poland in August, Slovak authorities said they thwarted a planned arson attack on a Ukrainian drone factory, and Poland, Lithuania and Bulgaria have all reported sabotage attacks on Starlink stations. A series of drone attacks on commercial ships has occurred in the Black Sea near the waters of NATO members Bulgaria and Romania. The later arson attempts against drone manufacturers, reported attacks on Starlink stations, and drone incidents involving commercial ships may relate to the Leipzig operation through temporal association, shared GRU infrastructure, a common political purpose, or independent opportunistic action; the supplied account does not establish common infrastructure or directing networks linking each subsequent gray-zone incident to the Leipzig operation, and timing alone does not attribute them to one operation.
European leaders have publicly warned about the risks and privately debated how best to respond. Merz said, “Russia is waging a war on Europe; not just on Ukraine, but also against us.” Secretary of State Marco Rubio warned that the escalation could spill into NATO countries and “quickly turn what is a war between two countries into a much broader and far more dangerous regional conflict.” Aides to Chancellor Friedrich Merz said Berlin would have considered invoking NATO’s Article 5 collective-defense provision if the Leipzig attack had caused large numbers of casualties; Article 5 commits alliance members to assist an ally subjected to an armed attack, though a response could range from diplomatic support to a military strike, and the provision has been invoked only once before, after the Sept. 11, 2001 terrorist attacks. The Article 5 discussion in the substrate presents casualty potential as a German condition for consideration, not as a formal casualty threshold within Article 5.
CIA Director John Ratcliffe traveled to Moscow in late August to revive negotiations and warn Russia against escalating its attacks on European allies; afterward, he personally warned European intelligence counterparts and selected political leaders that Moscow was intensifying sabotage operations, according to people who received the warnings. The CIA did not respond to a request for comment. Earlier this month, President Trump said he had reached a deal with Putin to provide diesel fuel to the U.S. and global markets to ease prices, and last week he halted sanctions that were set to be imposed on Russia under a bipartisan bill, drawing criticism from members of Congress. Trump said in a social-media post Sunday his decision on Russia was aimed at keeping Russia at the bargaining table and out of the war with Iran. The White House did not respond to a request for comment.
Evidence limits and unresolved questions
The substrate carries several discrete limits on what is known. The supplied report does not include a public written order from Putin; political authorization is source-attributed, not publicly documented. Smolyaninov’s EU and British sanctions reflect previous accusations that he directed Russian covert operations in Europe; sanctions alone do not prove his role in Leipzig. The public account does not fully map the internal reporting lines among the SSD, Smolyaninov, and Levushkin; it therefore supports organizational convergence rather than a fully documented direct chain. The reported post-attack warning from a Kremlin back channel to Berlin is consistent with Russian awareness but does not independently identify who authorized the operation. The supplied account does not establish common infrastructure or directing networks for each subsequent gray-zone incident; timing alone does not attribute them to one operation. The reported technical details describe the operation’s control and destructive mechanisms but do not establish why the drone that struck the Antonov aircraft failed to detonate.
The reported system became consequential because political authorization, military-intelligence organization, logistics, technical communications, and targeting converged; no single layer fully explains the operation. Political authorization alone would not place armed drones beside the airport; logistics alone would not explain why the operation targeted a cargo aircraft carrying military assistance; technical communications alone would not establish who authorized the mission. Targeted counter-measures against the SSD, the Serbian logistics network, or named operatives such as Smolyaninov or Levushkin would degrade the campaign’s operational capacity but would not remove the strategic driver; a negotiated settlement producing the concessions Russia sought, or a Russian decision to abandon those objectives, would. The third-country transit hub is a structural vulnerability, but targeting it would degrade future operations without addressing the strategic objective that drives them.
Analytical techniques used in this piece
This analysis applies the methods below. Each links to a short, plain-English explainer you can read and reuse.
- Root-Cause Analysis
- Traces a symptom back along its causal chain to the conditions that actually generated it.