Multiple Ozon Apps Removed from Google Play Following Sanctions on Ozon Bank
Several Android applications from Ozon have disappeared from Google Play, leaving users without access to the main marketplace client and related services through the official store.
The removed apps include Ozon Fresh, Ozon Seller, Ozon Job and Ozon Travel. Ozon confirmed that it had not breached Google Play policies, but the company has not disclosed the precise reasons behind the decision.
Owners of Android devices are now advised to obtain the applications from alternative official stores such as RuStore, AppGallery and Galaxy Store. Searching for APK files on random websites is strongly discouraged due to potential security threats.
The removals follow the earlier disappearance of the Ozon Bank application from Google Play after the bank was targeted by European Union sanctions. No official link between the sanctions and the broader app removals has been established so far.
Meanwhile, Apple users can still download Ozon applications via the App Store. The recent purge also affected the payment service Yandex Pay, which was removed from the App Store.
Already installed applications typically remain operational, yet users may encounter problems with updates and reinstallation after removal from the store. Ozon services continue to be available through other app stores and the web version.
Related articles
Russia's MinTsifry Flags Google Android Developer Verification Rules as Risk to Domestic Apps
Russia's Ministry of Digital Development is assessing new Google policies that will require developer registration for Android apps distributed outside Google Play. The changes, starting in select countries in 2026 and expanding globally in 2027, could block sideloading of Russian applications previously removed from official stores due to sanctions. Minister Maksut Shadaev described the scenario as a potential barrier where users may no longer freely install APK files from third-party sources. Google plans to retain advanced modes and ADB installation options with extra warnings for unverified apps. Custom firmware projects such as LineageOS have stated their devices will remain unaffected by the verification system. Russian banks, marketplaces, and other services that rely on direct APK distribution are viewed as the most exposed.
Rosfinmonitoring Denies Mass Bank Account Blocks Over Partial Data Matches with Sanctions Lists
Rosfinmonitoring has issued clarifications rejecting reports of potential widespread freezes of bank accounts due to partial matches between client data and records of individuals subject to asset freezes. The agency stressed that the draft law is not intended to penalize people who merely share surnames or have similar name transliterations with sanctioned persons. Criteria for determining partial matches have not yet been defined and will be established by a separate order only after the federal law is adopted and real cases are analyzed. The measure provides only for temporary suspension of a transaction rather than automatic refusal or indefinite account blocking. Earlier reports from Izvestia had warned that loosely defined partial-match rules could generate numerous false positives affecting ordinary clients.
Understanding GOST Cryptography Standards: A Practical Guide for Russian Developers
The article provides a beginner-friendly breakdown of Russian GOST cryptographic standards, separating the core functions of hashing, digital signatures, and encryption. It covers the evolution of GOST algorithms across three generations from the 1990s to the current 2012+ standards including Stribog, Kuznechik, and Magma. Detailed explanations address how PKCS#11 interfaces with hardware tokens, how X.509 certificates function as digital passports, and how formats like CAdES, XAdES, and PAdES package signatures for verification. Comparisons with Western equivalents such as SHA-256, RSA, and AES help developers map familiar concepts to GOST implementations. The guide emphasizes practical integration with tools like CryptoPro for tasks involving detached signatures and certificate requests in PKCS#10 and PKCS#12 containers.
Why Vulnerability Management Specialists Must Master Compliance: Closing All CVEs but Leaving admin:admin
The article explains how compliance has evolved from a paperwork exercise into a mandatory, heavily penalized process in Russian cybersecurity. New regulations such as FSTEC Order 117, turnover fines for personal data leaks, and Presidential Decree 250 impose strict timelines and personal liability for vulnerability management failures. It outlines three approaches to compliance, from doing nothing to building custom standards based on CIS Benchmarks and local requirements. The text stresses moving from reactive scanning to golden images that embed compliance controls before deployment. It highlights tools like MaxPatrol HCC, RedCheck, and ScanOVAL for automated checks and warns that technical patches alone are useless without proper configuration controls such as strong passwords.