AntiMalware•November 19, 2026•🇷🇺Translated from Russian

False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry

Social media users in Russia are encountering misleading posts claiming that citizens face a fine of 50,000 rubles for failing to submit their bank card details to a new unified registry. The information has been debunked by the project Lapsa Media, which determined that the warning images were created using AI and contain numerous factual errors and typos.

According to official clarifications, ordinary citizens do not need to submit any data themselves. Banks are solely responsible for transferring information about active payment cards to the registry. The Bank of Russia has confirmed that the unified system for recording payment cards is indeed under development, with NSPK designated as the system operator.

Under the new rules, banks must submit card numbers, card types, and the INN of each cardholder to the registry by September 1, 2027. Beginning on that date, banks will check the total number of cards held by a client before issuing any new card. The restriction is set at a maximum of 20 cards per client and is intended to prevent the mass issuance of cards that are later handed over to fraudsters.

Importantly, cards issued before the limit takes effect will continue to function even if their number exceeds 20. No forced closure of existing cards is planned. The measure forms part of broader efforts to strengthen protection against fraud in the Russian banking sector.

Related articles

Habr•Policy & Regulation

Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks

The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.

Habr•Policy & Regulation

Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite

A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.

Habr•Policy & Regulation

Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure

The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.

Habr•Policy & Regulation

Recovering Losses from Hosting Providers After Cyberattacks: Legal Steps for Russian Businesses

Russian entrepreneurs frequently encounter service disruptions when hosting providers suffer cyberattacks, leading to inaccessible websites, lost backups, and damaged virtual server images. Under Articles 15 and 393 of the Russian Civil Code, businesses hold the right to claim damages, yet success depends on contract terms, provider obligations, incident circumstances, and proper evidence collection. The guidance outlines five key actions: documenting the attack effects through official notices, error logs, and monitoring data; calculating real damages and lost profits with supporting contracts and payment records; reviewing the service agreement or public offer for backup responsibilities and liability limitations; submitting a formal claim that details violated obligations and requests compensation; and assessing court prospects if the provider refuses payment. Judicial practice shows that cyberattacks alone neither automatically exempt providers from liability nor guarantee recovery. Companies are advised to retain applicable contract versions in advance to streamline future claims.