Vladimir Putin's reported plan to hit back at the UK in "two key attacks" centers on sabotage and cyber operations carried out not by Russian troops but by proxy agents, intelligence officers, and hacker groups. Analysts describe a retaliation playbook that pairs physical sabotage of undersea cables or energy infrastructure with disruptive cyber strikes on government and utility networks. The people tasked with executing it would likely be GRU and SVR operatives working through criminal proxies and hacktivist fronts rather than uniformed military units.

The retaliation mechanism: sabotage plus cyber

The phrase "two key attacks" reflects a dual-track design rather than two specific targets. Track one is physical: covert action against infrastructure that is hard to guard and expensive to repair. Track two is digital: disabling or degrading networks that coordinate the UK's response. The two tracks reinforce each other because a cyber strike can blind monitoring systems while a physical team moves against a cable or substation.

Physical sabotage of subsea infrastructure is the most discussed option. Undersea cables carry the overwhelming majority of international data traffic, including financial messaging and military communications. A cutting operation requires a surface vessel or a trawler with a modified anchor, a covert team, and precise location data. Russia has a dedicated naval unit, the Main Directorate of Deep-Sea Research, often called GUGI, that operates specialized submersibles and research ships. Those vessels appear near cable routes and wind farms in the North Sea and around the UK coast with regularity.

Cyber operations are cheaper to mount and harder to attribute. The GRU's known units, including Unit 26165 and Unit 74455, have a documented history of attacking Ukrainian, NATO, and Western targets. Those units work through contractors and criminal forums to distance the Kremlin from the payload. The UK's National Cyber Security Centre has repeatedly attributed disruptive campaigns to Russian state actors, which gives analysts a pattern to project forward.

The mechanism matters more than the specific target list. A sabotage campaign works by imposing costs the UK cannot easily absorb, not by achieving battlefield effects. The UK's geography makes it dependent on cables crossing the Atlantic and the North Sea, so a small number of cuts can degrade capacity. The UK's grid is interconnected with European grids, so a cyber strike on one operator can propagate. This is coercion through infrastructure, not conquest through force.

A plain-language way to frame it: the plan targets the plumbing of British economic and military life, and it uses deniable hands to do it.

The people who would carry out the mission

The operators behind such a plan would sit in three layers. The first layer is the intelligence services: the GRU for sabotage and cyber, the SVR for political influence and agent handling, and the FSB for domestic control and some overseas operations. The second layer is the proxy force: criminal ransomware groups, hacktivist collectives, and recruited local agents. The third layer is the unwitting enabler: shipping companies, logistics firms, and individuals who sell access or services without knowing the buyer.

Attribution is the central difficulty. A cable cut that looks like an accident, a ransomware attack that looks like a criminal shakedown, and a hacktivist leak that looks like amateur activism all provide plausible cover. Western governments have grown faster at attributing these operations publicly, but the legal and diplomatic response still lags the operational tempo. That gap is exactly what a retaliation campaign exploits.

The proxy layer includes groups that operate under shifting names and claim ideological motives. Some are directly controlled by intelligence officers; others are tolerated criminal enterprises that occasionally take direction. This distinction matters for response because a state-to-state retaliation ladder does not map cleanly onto a criminal affiliate.

A counterintuitive detail is that the most damaging proxy operations may not be the most sophisticated. A simple ransomware strike on a hospital or water utility, launched by a criminal group that happens to align with Russian interests, creates disproportionate disruption without any detectable GRU fingerprint. The Kremlin gets the effect and avoids the attribution.

Quantified context: why two attacks can matter

Scale explains why a small number of operations produces outsized effects. Roughly 99 percent of intercontinental data traffic moves through subsea cables, and the UK is a major landing point for transatlantic routes. A single cable cut can reduce capacity on a route by a significant fraction until traffic is rerouted, and repair vessels can take days to weeks to reach and fix a deep-water break.

Cyber disruption scales differently. A ransomware attack on a single managed service provider can cascade to dozens of downstream clients, because small firms often share the same hosting and backup vendor. The 2024 attack on a UK pathology services provider disrupted blood testing across multiple hospitals for weeks, showing how one compromise propagates through a shared supplier. That pattern, not the headline target, defines most real-world damage.

Cost estimates for infrastructure repair vary widely by depth and location. A shallow-water cable repair may run into the low millions of dollars, while a deep-ocean repair can exceed USD 10 million and take weeks of ship time. The economic damage from lost connectivity typically dwarfs the repair cost, which is why insurers and governments treat cable security as a strategic issue.

Timelines also favor the attacker. A cyber intrusion can be staged for months before activation, with access sold or handed off between groups. A physical sabotage operation needs vessel positioning, weather windows, and a recovery plan. The cyber track sets the tempo; the physical track provides the escalation signal.

Comparison table: retaliation options and their signatures

Option Attribution difficulty Time to effect Recovery burden Deniability
Undersea cable sabotage High Days Weeks to months High (looks accidental)
Ransomware on utilities High Hours Days to weeks High (criminal cover)
Spear-phishing government networks Medium Days Days Medium
GPS jamming of aviation Low Immediate Hours Low (traced to emitter)
Disinformation and leaks High Days Ongoing High (hacktivist front)
Physical attack on substation Medium Hours Days Medium (local evidence)

The table shows the trade-off every planner faces: the operations with the best deniability are also the slowest to produce an unambiguous signal. If the goal is to communicate resolve to a domestic audience while avoiding a clear act of war, the cyber and cable tracks are the rational choice.

Timeline of a likely operation

Phase Approximate duration Activity
Preparation 6-18 months Recruit proxies, map cables, stage access
Positioning Weeks Move vessels, place agents, test payloads
Activation Hours Launch cyber strike, trigger physical team
Disruption Days Capacity loss, service outages, media panic
Attribution Days to weeks Forensics, intelligence sharing, public naming
Response Weeks Sanctions, expulsions, hardening measures
Repair Weeks to months Cable ships, patching, restoration

The phase that matters most for defenders is preparation, because it precedes any observable attack. Most of the leverage against a sabotage campaign sits in detecting the staging, not in reacting to the strike.

Edge cases and red-flag warnings

Not every cable fault or outage is an attack. Fishing anchors, seismic activity, and equipment failure account for the majority of real incidents. Treating every disruption as hostile action produces false alarms and erodes credibility. The hard problem is distinguishing a deliberate cut from an accident fast enough to respond while evidence is fresh.

A vessel loitering over a cable route with its transponder off deserves scrutiny, but innocent ships also disable transponders for legitimate reasons. Ransomware demands in cryptocurrency are common criminal behavior, so payment demands alone do not prove state involvement. A hacktivist group claiming a leak may be a front, a genuine amateur, or a criminal crew rebranding, and the three require different responses. Public attribution without supporting evidence can be politically costly if it is later contradicted. Overreliance on a single intelligence source creates a single point of failure in the response chain.

A professional caveat: the boundary between tolerated criminal activity and directed state action is blurry by design. Analysts who insist on a clean distinction will misread operations that are deliberately built to sit in the gray zone.

Practical actions: how to harden against the two-track threat

Defenders can act on concrete thresholds rather than waiting for attribution.

Map every cable landing, substation, and shared service provider that supports critical operations, and assign an owner to each. Set a recovery time objective of 24 hours or less for the systems that coordinate incident response, and test it quarterly. Require multi-factor authentication and offline backups for any vendor that touches more than 1,000 users or any safety-critical system. Treat any single managed service provider serving more than a handful of essential clients as a systemic risk, and demand independent backup paths. Establish a pre-agreed attribution and communication protocol so that public statements are not improvised during an outage.

For individuals and small organizations, the practical threshold is simpler: assume that shared vendors are targets, keep offline copies of essential records, and know who to call when the primary channel goes down. These steps do not stop a state campaign, but they shorten the disruption window that a campaign depends on.

Limitations of what can be concluded

Public reporting on specific Russian plans is fragmentary and often based on intelligence assessments that governments release selectively. No open-source analysis can confirm that a particular "two key attacks" plan exists in operational form, only that the pattern matches documented Russian behavior. The mechanisms described here are stable and well evidenced; the specific targets and timing are not. Anyone presenting a precise list of named targets should be treated with skepticism unless a government has attributed it publicly.

The dual-track model also has a response problem that open analysis cannot solve. Attribution takes time, and the political and legal thresholds for retaliation are set by governments, not analysts. The gap between what is known and what can be proven is the space in which these campaigns operate.

This article is general educational information about geopolitical and cybersecurity risk, not a diagnosis, legal opinion, or investment recommendation. It does not promise any outcome and is not a substitute for advice from a qualified security, legal, or financial professional. For immediate danger or a live cybersecurity incident, contact local emergency services or your national cyber response authority.