Google Tests Third-Party App Store Support in Play Store Following Epic Games Antitrust Ruling
Google is currently testing several new features in the Play Store, including an experimental section called Play Labs, support for third-party app stores, and an expanded search bar. These changes have been identified in a recent version of the service, although most of the new capabilities remain inaccessible to regular users at this time.
The most significant development is the planned ability to install alternative app marketplaces directly from Google Play. The company had previously confirmed work on this functionality, which stems from the ongoing antitrust proceedings involving Google and Epic Games. After the settlement between the two companies was withdrawn, the 2024 court ruling once again became active, requiring greater openness to competing stores.
The new menu option for third-party stores was discovered only after direct intervention in the application code. It appears in an additional menu but currently returns an error when users attempt to open an alternative marketplace. In the same area, researchers also found Play Labs, an experimental section where users will likely be able to test upcoming store features before they reach general availability. Google already uses similar experimental sections in other products, including its main search engine.
While Play Labs and the third-party store option are not yet functional, the updated search interface is already working. Google is preparing a two-line search panel designed to accommodate longer natural-language queries, accompanied by an Ask Store prompt. Instead of entering a short app name, users will be encouraged to describe their needs in detail, after which the store will attempt to suggest suitable applications.
These experiments follow recent Play Store improvements such as enhanced search capabilities and the option to test widgets during app installation. Broader rollout of the new search panel is expected in the coming weeks. However, APK analysis only reveals features currently under development, and Google retains the option to modify, postpone, or abandon any of them before release.
The direction of these changes is notable: the main Android app store is preparing to distribute competing marketplaces to users, effectively turning competition itself into a feature that can be installed through Google Play.
Related articles
Implementing 2FA Kubernetes Access via Gateway API, Dex and MULTIDIRECTORY
A Russian cybersecurity company replaced static kubeconfig files with corporate accounts and mandatory 2FA for its Talos Linux Kubernetes clusters. The solution routes all authentication through a single FQDN using NGINX Gateway Fabric, Dex as an OIDC provider connected to MULTIDIRECTORY via LDAP, and kube-oidc-proxy for token validation and impersonation. Groups stored in the directory are passed directly into RBAC bindings, eliminating manual certificate management. A lightweight Python service dynamically generates kubeconfig files that contain no secrets. The team documented several Gateway API migration pitfalls including namespace route restrictions and BackendTLSPolicy hostname validation. The approach keeps the entire configuration in Git and avoids modifying kube-apiserver flags.
Windows File System Tunneling Preserves Old File Metadata for Legacy Compatibility
Microsoft has clarified that Windows sometimes assigns creation dates from deleted files to new ones due to a long-standing mechanism called File System Tunneling. The feature keeps metadata in a short-term cache for about 15 seconds after a file is deleted or renamed. If a new file with the same name is created quickly in the same folder, it inherits the previous file's timestamps and short-to-long name mappings. This behavior exists to support safe saving patterns used by many applications and to maintain compatibility with old DOS-era 8.3 filename formats. The actual file content is never restored, only the metadata. The cache is temporary and clears over time, so the effect does not occur with files deleted long ago. The explanation came after users noticed unexpected dates in Windows Explorer and questioned whether it was a bug.
Amazon Confirms Irrecoverable Data Loss in UAE and Bahrain Data Centers After Drone Attacks
Amazon Web Services has officially confirmed that data stored in specific availability zones within its Middle East regions was permanently destroyed following physical attacks on data centers in the UAE and Bahrain. The incidents began on March 1 and continued through April and July, damaging infrastructure tied to AI development projects. In the UAE region mec1, only zone mec1-az2 was completely destroyed with no external backups, while mec1-az3 suffered severe damage and mec1-az1 remained operational but overloaded. All three zones in the Bahrain region me-south-1 were rendered inoperable. AWS had spent six months attempting recovery before issuing the final statement on September 15, 2026, and has advised customers to migrate workloads to unaffected regions. The event highlights growing risks to data from physical-world attacks beyond traditional network threats.
Bots Overload OT Commerce Store on OT Box, Spike Paid OTAPI Calls Mistaken for DDoS Attack
An online store running OT Commerce experienced CPU loads reaching 98-100% and a 6-7x increase in paid OTAPI calls over three days due to automated bot traffic rather than a traditional DDoS. The site owner had already deployed a paid anti-bot module on the VPS, yet behavioral bots continued to bypass protections and force expensive calls to the external OTAPI platform for product data from Taobao, Tmall, 1688 and other marketplaces. Traffic analysis after switching to the CRONARMOR WAF revealed that 41.9% of page requests were automated, with 99.3% of early-stage automation blocked before reaching the origin server. Only 0.5% were behavioral bots visible in analytics, while legitimate search crawlers accounted for 27,190 requests that were explicitly allowed. The WAF approach stopped requests at the reverse proxy layer, preventing PHP execution, database queries and OTAPI billing events on the origin. Post-deployment CPU dropped to single digits for most of the day, eliminating both performance issues and the anomalous rise in paid API usage.