Peskov's word problem: when 'special military operation' becomes 'war' on Russian state TV
Moscow's spokesperson is now blaming someone — anyone — for the lexical slide from 'special military operation' to 'war'. The slippage says more about the Kremlin's information position than any briefing room confession.

At 13:14 UTC on 5 July 2026, Ukraine's TSN news channel flagged a linguistic contortion at the heart of the Kremlin's information war: Russian presidential spokesperson Dmitry Peskov has been forced to locate a culprit for the slow, four-year slide from the official designation specialnaya voyennaya operatsiya — "special military operation" — to the plain word voyna, war. TSN's framing treats the hunt for a scapegoat as a story in itself. The framing is right.
The shift matters because the language Moscow uses to describe the invasion has never been a cosmetic choice. It is a legal designation, a censorship boundary, and a signal to the Russian public about what kind of conflict the country is supposedly fighting. Watching that vocabulary corrode in real time is watching the information architecture of the war lose its grip.
What Peskov is actually admitting
The Russian state's position, codified in a 2022 administrative-code amendment and reinforced through subsequent rulings, treats the public equation of the invasion with a "war" as a finable offence. Independent outlets that crossed the line — Novaya Gazeta, Dozhd, the Moscow Times — paid for it in licensing actions, foreign-agent designations, or exile. The vocabulary was the gate.
Peskov's search for "someone to blame," as TSN reports, is therefore a tacit acknowledgment that the gate has worn down. Russian-language social media, Telegram channels, regional press, and even some state-media interviewers have been using voyna with increasing ease. The official designation survives in prepared presidential texts and on the evening news ticker; it has thinned almost everywhere else. The Kremlin's information position is not collapsing — Russian state television still runs nightly — but the lexical discipline that made the position work is fraying at the seams.
The structural read
Every wartime state tries to control the lexicon that describes its war. The United States spent the better part of two decades trying to retire "war on terror" as a category name; Israel has long managed the legal frame around "operations" versus "wars" in domestic debate. What is distinctive in the Russian case is the gap between the formal designation and the lived vocabulary of the people who are supposed to use it.
The reason is partly demographic. Roughly four years in, the cohort of Russians with a personal stake in the war — servicemembers, their families, the civilians in border regions absorbing drone and cross-border strikes — has grown large enough that euphemism feels insulting to them. Soldiers posting from the front rarely write SVO; they write voyna. The same is true of regional governors describing attacks on their territory. The vocabulary of the war has migrated from the men at the front to the press pool, and the press pool is where Peskov operates.
Why the scapegoat hunt matters
When a political spokesperson is asked to explain why a controlled term has lost control, the answer usually points to a single villain — a foreign outlet, a Telegram channel, a hostile intelligence service. That pointing exercise is itself the product. It tells the domestic audience that the lexical drift is imported, not grown; that the regime's information discipline has not failed, it has been attacked.
The harder truth, which the scapegoat framing works to suppress, is that information discipline fails from the inside when the war it is meant to describe starts to look like the war it is. A "special operation" is, by definition, bounded — in scope, in geography, in time, in casualty profile. The full-scale invasion of Ukraine that began in February 2022 has never matched that description. Each year of grinding attritional combat, each new wave of mobilisation, each cross-border strike into Belgorod or Kursk oblasts has widened the gap between the term and the thing. Eventually, the term loses.
Stakes and what to watch next
The stakes of Peskov's lexical problem are not symbolic. They shape whether Russians can be prosecuted for what they say about the war, whether regional journalists can report on strikes honestly, and whether the post-war information settlement in Russia will look like an amnesty or a purge. If the regime decides to formally rename the conflict — a step several Russian commentators have floated — that would represent the most significant loosening of wartime information control since 2022. If it instead doubles down on enforcement, expect a new round of cases against regional outlets and Telegram admins.
The Ukrainian angle is structural rather than incidental. Kyiv has a direct interest in every crack in the Russian information position. The longer the war is called a war inside Russia, the harder it is to argue that it can be ended by a single decree. That is the quiet dividend Western readers should keep on the books: a vocabulary that finally fits the conflict is, in itself, a constraint on the regime's optionality.
What remains uncertain is whether Peskov's hunt for a culprit will produce a name — and whether that name will be domestic or foreign. Russian-language Telegram channels have speculated in both directions, and the Kremlin has given no signal. The one thing the sources agree on is that the hunt is now underway, which is itself the admission the spokesperson would rather not have made.
Desk note: Monexus is treating TSN's report on Peskov's framing exercise as the lede, not the wire-of-record claim that "Russia has admitted the war is a war." The lexical drift is real, sourced, and structurally important; the rhetorical leap to "Kremlin concedes war" is not. Sources are kept deliberately tight to what TSN flagged and what the relevant background materials support.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/TSN_ua