Several reports describe a scenario in which about ten clones of the RuStore marketplace, developed by VK with the support of the Ministry of Digital Development of the Russian Federation, appear within Xiaomi’s Mi GetApps branded app store. This situation has been highlighted by the Vedomosti publication, which notes that these clones are not the real RuStore experience but rather impersonations hosted in a separate storefront ecosystem. The underlying concern is that a well-known service is being repackaged under a trusted brand, creating a false sense of security for users who may be unaware of the distinction.
RuStore is a native application store with its own ecosystem and branding, while the versions masquerading as RuStore inside Mi GetApps function differently. After installation, the RuStore icon shows up on the device home screen, yet behind that icon lies another set of apps with different purposes, such as a calculator, 2GIS maps, desktop wallpapers, and additional software. This deceptive layering means users may believe they are launching the official RuStore client when, in reality, they are interacting with unrelated applications that simply carry the RuStore symbol.
Vedomosti cites data from Mi GetApps indicating that these services have been present in the store since at least autumn, with two of them installed as early as January 2024. The pattern suggests a deliberate attempt to piggyback on the RuStore brand, creating an illusion of provenance and reliability while distributing unrelated functionality. In practical terms, these clones are not designed to deliver malicious payloads; instead, they prioritize ad display and revenue generation for their creators, exploiting the brand association to attract downloads and impressions. Still, the repetitive advertising and potential user confusion present real risk for consumer trust and brand integrity.
Information security professionals consulted for the reporting noted that while such clones typically do not carry harmful payloads, their presence constitutes a form of brand misrepresentation and software repackaging. The immediacy of the risk comes from user familiarity with RuStore and the possibility of accidental installation, which can lead to privacy concerns and unwanted data collection. The broader takeaway is that these replicas leverage a familiar name to monetize user interactions, raising questions about app store governance, vetting standards, and the responsibilities of platform owners to curb deceptive listings.
VK has publicly affirmed that RuStore holds registered and protected trademarks and stressed that the RuStore client is not distributed through third-party app stores. The company reiterated that the official RuStore client is available solely from the project’s official website, underscoring the importance of sourcing software from trusted channels. The claim points to a controlled distribution model designed to minimize counterfeit or tampered experiences, while also signaling a commitment to brand stewardship and user safety. This stance appears to be part of a broader effort to clarify the conditions under which RuStore operates and to deter unauthorized reproductions in competitive app ecosystems.
In Russia, industry observers have also discussed related initiatives and experiments around alternative app stores for popular platforms, with NashStore cited as an example of a project aimed at offering another distribution pathway. These developments reflect a competitive landscape in which mobile storefronts, branding, and user trust intersect with regulatory oversight, developer rights, and consumer protection. The ongoing discourse emphasizes the need for transparent vetting processes, clear labeling of official versus clone software, and robust user education to help audiences distinguish legitimate stores from imitators. The situation also highlights how brand signals can influence user choices in crowded marketplaces, reinforcing the call for stronger verification mechanisms and consistent messaging from platform operators and developers alike.