Habr•October 12, 2026•🇷🇺Translated from Russian

Passphrases vs. Leetspeak Passwords: Why Four Random Words Outperform P@ssw0rd!2026

All of us have faced registration forms that behave more strictly than a nightclub bouncer. The form demands an uppercase letter, a digit, and a special character, rejecting an eight-letter password as insufficiently elegant. Users respond by capitalizing the first letter of a favorite word, appending an exclamation mark and the current year, and watching the indicator turn green. The result is P@ssw0rd!2026, a string that satisfies the strictest policy yet ranks among the first thousand guesses any attacker will try before finishing morning coffee.

Password strength is measured in bits of entropy. Each additional bit doubles the number of possible combinations. Forty bits equal roughly one trillion possibilities; sixty bits reach one quintillion. The human eye cannot judge this arithmetic. It sees symbols and mixed case and awards high marks, while an attacker cares only about predictability.

How passwords are stored

Proper sites never store the plaintext password. Instead they run it through a one-way hashing function and keep only the resulting digest. Fast legacy hashes allow video-card farms to test billions of candidates per second. Modern algorithms such as Argon2 deliberately slow the process and consume large amounts of memory, turning the same farm into a bottleneck. Salting each hash further prevents attackers from testing one candidate against every account simultaneously.

Four random words versus leetspeak

Consider the passphrase корова-лампа-поезд-ромашка (cow-lamp-train-daisy). When each word is chosen uniformly from a 50,000-word Russian noun list, one word contributes roughly 15.5 bits and four words together reach about 62 bits—more than four quintillion combinations. Against a fast hash at 100 billion guesses per second, the average cracking time is roughly nine months. With Argon2 the same 62 bits stretch into decades.

The visually impressive P@ssw0rd!2026 begins with the dictionary word “password,” already first on every attacker’s list. Leetspeak substitutions, appended years, and exclamation marks are all codified in automated rule sets. Tools apply hundreds of such transformations instantly, so the candidate is tested within the first seconds of an offline attack. Its effective entropy collapses from an imagined 85 bits to single digits.

Why length works only with randomness

Length alone is insufficient if the phrase follows predictable patterns. A meaningful sentence such as “myfavoritecatbarsik” remains vulnerable to dictionary and Markov-chain attacks. True randomness is supplied by generators such as diceware, which selects words by rolling physical dice against published word lists. Four words form a practical minimum; five words provide a comfortable margin. A single capital letter and a separator add a few extra bits but are secondary to the random selection itself.

Passphrases are also easier to dictate over the phone and to type on awkward keyboards. They reduce password reuse across sites, a common consequence of hard-to-remember complex strings. When services support passkeys, the entire problem of memorizable secrets disappears because no secret exists that can be brute-forced.

The central lesson is that strength resides in the method of creation, not in the appearance of the final string. Registration forms that reward symbols and digits therefore measure the wrong property. A random four-word passphrase defeats offline attacks far more effectively than any number of exclamation marks.

Related articles

Habr•Policy & Regulation

Building the Foundation of Digital Trust: Why Identity Security Remains Undervalued

Identity Security is presented as one of the most underestimated pillars of cybersecurity because granting access involves trusting individuals with sensitive information and systems. The article examines the deep intersection of IT and security functions, the costs of manual access errors, and the need to align business processes with technical controls. It references a 2026 Identity Conf study showing 43.5% of organizations experienced errors in manual rights assignment and 33.5% left access for former employees. Recommendations draw on NIST Human-Centered Cybersecurity concepts, SP 800-53, and Russian FSTEC Order No. 117 to design lifecycle processes covering account provisioning, privilege reviews, and continuous monitoring. Models such as RBAC and ABAC are discussed alongside IGA and IdM solutions to ensure business permissions map correctly to application rights. The piece stresses that successful projects require joint IT and security efforts from the initial survey through pilot and acceptance phases while measuring both risk reduction and operational efficiency.

AntiMalware•Policy & Regulation

VK Files Lawsuit in EU Court Seeking to Overturn Sanctions Imposed in July

Russian internet company VK has submitted a formal challenge to the European Union's sanctions regime by filing a case with the Court of Justice of the European Union. The company argues that the restrictions placed on VK and its subsidiary Communication Platform LLC are both unjustified and unlawful. The lawsuit, registered under case number T-664/26 on 7 October, directly contests the July sanctions that targeted the developer of the MAX messenger. Earlier restrictions had already led to the removal of multiple VK ecosystem applications from Apple App Store and Google Play, forcing users toward alternative distribution channels such as RuStore, Huawei AppGallery, Samsung Galaxy Store and Xiaomi GetApps. While installed Android applications continue to function and receive updates, iOS users face disrupted push notifications after the apps were delisted. The legal action itself does not automatically restore app availability in the affected stores.

Securitylab•Policy & Regulation

VPN Rules in Russia 2026: No Fine for Ordinary Users but Strict Penalties for Advertising and Extremist Content Access

As of September 2026, Russia maintains no separate administrative fine for ordinary citizens simply connecting to a VPN service. Responsibility arises only for specific actions such as deliberately searching for known extremist materials, advertising tools to bypass restrictions, or failing to comply with Roskomnadzor demands as a service operator. Corporate VPNs used for remote access to company networks remain fully legal under exceptions in Article 15.8 of Law No. 149-FZ. New provisions in the Code of Administrative Offenses, including Articles 13.53, 13.52 and 14.3 introduced by Laws 281-FZ and 282-FZ, impose fines ranging from 3,000 to 500,000 rubles depending on the violation and the offender category. The rules distinguish clearly between end users, service owners and advertisers. VPN technology itself is not banned, yet public services face ongoing blocking and operators must integrate with state filtering systems. The material reflects the regulatory situation on 24 September 2026.

Habr•Policy & Regulation

Troubleshooting Erroneous TSPU Blocks: How Admins Can Collaborate with Russian Regulators

A Moneta client outage traced back to erroneous filtering on Russia's TSPU system rather than internal infrastructure or DDoS protection. Engineers used curl, traceroute, nping, and custom Python scripts to confirm TCP payload-based blocking after the handshake. The team submitted a request via the VTS personal account, received partial acceptance status, then escalated to DCOA and SSOP to obtain the specific TSPU site number. Detailed network traces and active traffic were required for diagnostics. The case highlights coordination challenges between operators, DCOA, and SSOP when erroneous blocks occur on information resources.