In what appeared to be a routine background update within Google Chrome, privacy researchers have raised concerns over a potentially problematic update after reports revealed that the browser may have silently downloaded a nearly 4GB artificial intelligence model onto certain systems without explicit user approval.
Known as Gemini Nano, this component enables local AI processing directly on laptops and smartphones rather than relying solely on cloud infrastructure. However, cybersecurity observers and digital rights advocates contend that the deployment was inadequately transparent, especially because the installation of an AI package requiring significant storage was not visible to users.
The disclosure, amplified by a Swedish computer scientist and privacy.
Google’s incremental deployment of Gemini Nano, a lightweight large language model designed to execute on-device operations such as text optimization and automated scam detection, is revealed by an investigation into the browser’s filesystem mechanics.
The background payload is the result of this incremental deployment.
Hanff’s diagnostic tests are supported by a system-level analysis, which shows that the browser initiates an independent directory named OptGuideOnDeviceModel when a machine running recent Chrome iterations satisfies certain hardware requirements, and that the browser extracts weights.bin, which is a 4- gigabyte binary file.
Hanff’s diagnostic tests are supported by a system-level analysis, which shows that the browser initiates an independent directory named OptGuideOnDeviceModel when a machine running recent Chrome iterations satisfies certain hardware requirements, and that the browser extracts weights.bin, which is a 4- gigabyte binary file.
Due to the architecture’s use of default active optimization flags rather than user-triggered prompts, the local installation does not require explicit confirmation dialogs. This practice has drawn intense scrutiny due to issues related to storage overhead, metered network data consumption, and compliance with regional data governance protocols.
It has been stated by Google that users may mitigate the automated download sequence by deleting the On-device AI program or the Optimization Guide parameters using internal settings (chrome://flags). However, the lack of a standard, upstream opt-in mechanism before writing multigigabyte binaries to a user’s persistent storage has fundamentally heightened the debate over digital sovereignty on the client’s side.
A clean Apple Silicon profile has been audited to empirically isolate this persistent behavior beyond individual telemetry reports, using the native macOS kernel-level filesystem auditing daemon, .fseventsd.
In the absence of application-layer logging, this low-level mechanism records transactional file operations, which results in a tamper-proof ledger of Chrome’s execution pipeline which is unmodified by external application updates.
In the absence of application-layer logging, this low-level mechanism records transactional file operations, which results in a tamper-proof ledger of Chrome’s execution pipeline which is unmodified by external application updates.
As a result of the resulting data stream, it became evident that even when users manually purge the payload, which is mapped to mode 600 on macOS, the Local State configuration file retains the target installation.
This automated download loop is initiated once the client intercepts a new synchronization packet from Google’s central variations server confirming profile eligibility as soon as the client intercepts it.
This automated download loop is initiated once the client intercepts a new synchronization packet from Google’s central variations server confirming profile eligibility as soon as the client intercepts it.
The forced re-allocation of macOS resources on Mac OS is consistent with deletion-resistance patterns that have been extensively documented across Windows environments, thus confirming the silent overhead as a design constant across various desktop operating systems and not an isolated platform problem.
Content was cut in order to protect the source.Please visit the source for the rest of the article.
This article has been indexed from CySecurity News – Latest Information Security and Hacking Incidents
Read the original article: