Loading story…
Leaked screenshots and a screen recording from a Chromium Issue Tracker bug report revealed an early look at Google’s internal “Aluminum OS” (ALOS) project—an apparent desktop-oriented Android build tied to Google’s long-running effort to consolidate Android and ChromeOS into a single platform. The report was subsequently made private, but not before the media captured the visuals, which are described as the first “official” visual evidence of the desktop Android interface.
The leak indicates the build ZL1A.260119.001.A1 running on an HP Elite Dragonfly/HP Chromebook-class device using an Intel 12th-gen (Alder Lake-U) x86 processor, suggesting testing on existing Chromebook hardware. Visible UI changes include a desktop-style bar optimized for larger screens (with time/date placement changes), desktop multitasking (side-by-side), and Chrome with extension support; one account also notes prominent Gemini and screen-recording icons, implying potential “AI-native” integration. Overall, the material points to a ChromeOS successor or alternative desktop experience built on Android rather than a conventional ChromeOS evolution.
See attribution, scope, and your downstream exposure.
2 events from the most recent confirmed update back to the earliest known activity.
Coverage of the leak described a desktop-optimized Android interface with a persistent status bar, split-screen multitasking, ChromeOS-like window controls, and an Extensions button in Chrome. The underlying bug report was later restricted or made private after the screenshots and related media were noticed.
A Chromium Issue Tracker bug report inadvertently exposed screenshots and details of Google's in-development desktop-oriented Android environment, including references to the codename ALOS/Aluminum OS. The leak showed the software running on an HP Elite Dragonfly Chromebook with an Android 16-based build.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
4 references tracked. Mallory keeps watching after this page renders.
zdnet.com
Open sourcetomshardware.com
Open sourcesecurityonline.info
Open source9to5google.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google Chrome is reportedly downloading a roughly 4GB file, `weights.bin`, onto some users’ devices as part of its on-device **Gemini Nano** AI features, prompting complaints that the transfer can occur without clear notice. Reports said the file appears in Chrome user data directories on eligible systems and may be fetched in the background during normal browsing, with one researcher citing a controlled macOS test and filesystem logs that showed Chrome creating the model directory and downloading the payload automatically. The file is described as part of Chrome’s local AI stack rather than malware, enabling faster processing, offline capabilities, and reduced reliance on cloud services, but critics said users may not realize it has been installed and that deleting it alone may not stop it from returning. Coverage said the download is tied to Chrome’s **On-device AI** setting, and users seeking to remove it more permanently must delete the file and disable that feature; the practice has also triggered claims that silent multi-gigabyte downloads could raise transparency, privacy, bandwidth, cost, and environmental concerns, including possible scrutiny under EU privacy rules.
Jun 29, 2026
Google has released **Chrome 151** to the stable channel, delivering a mix of user-facing, enterprise, and developer changes in the Chromium-based browser. The update adds new **Gemini** AI integrations, expands **Safe Browsing** protections, and improves PDF handling, while Google continues to distinguish Chrome from upstream Chromium through bundled components such as Google API integration, DRM support, and other Chrome-specific services. The release also keeps the **Extended Stable** channel available and indicates that **Chrome 152** is planned as the next major version. Chrome 151 also advances Google's transition away from legacy extensions by further restricting **Manifest V2** add-ons, though enterprises retain a temporary policy option to allow older MV2 extensions during migration. On the platform side, the browser drops support for **macOS 12** and now targets **macOS 13+**, while additional legacy browser features and APIs are being removed or deprecated, including older XML/XSLT-related functionality. The release further introduces web-platform updates for developers, including new HTML and `PerformanceObserver` capabilities, alongside broader changes affecting Windows, Linux, and macOS deployments.
Jul 30, 2026
Google's upcoming **Android 17** release is being discussed through early beta builds, leaks, and hands-on coverage of new AI-assisted features. Reported changes include a broader visual redesign tied to *Material 3 Expressive*, possible blur-heavy interface elements, and additional privacy-focused updates expected to be highlighted during the platform's public rollout. Early testing by Google and device makers indicates the next Android version is already in active development ahead of a likely mid-year stable release. One reported capability is **AI-powered notification summaries** on supported Pixel devices, which condense long messages and display them on the lock screen using on-device processing. That feature appears consistent with the broader push toward AI enhancements in Android, but the hands-on report focuses on current Pixel functionality rather than the broader Android 17 leak cycle. The material is **not fluff** because it contains substantive product and platform details with security and privacy implications, even though it is not about a breach, exploit, or vulnerability disclosure.
Jun 29, 2026