Loading story…
Google has introduced an enhanced autofill feature in Chrome that allows users to store and automatically fill in sensitive personal information, including driver's license numbers, passport numbers, and vehicle identification details such as license plates and VINs. The feature is opt-in, requiring users to manually enable it, and Google emphasizes that all stored data is encrypted and only used with explicit user confirmation. The update aims to streamline the process of completing complex online forms and is rolling out globally across all languages, with support for additional data types expected in the future.
While the convenience of this feature is clear, security experts have raised concerns about the risks of concentrating sensitive information in a single location. Although Google asserts that users remain in full control of their data and that strong privacy protections are in place, experts warn that a compromised Google account could expose not only emails but also any personal information stored via autofill. The recent exposure of millions of Gmail-linked credentials, though unrelated to autofill, highlights the broader risks of storing sensitive data online and underscores the need for users to carefully weigh convenience against potential security consequences.
See attribution, scope, and your downstream exposure.
1 event from the most recent confirmed update back to the earliest known activity.
Google expanded Chrome Autofill to support storing and filling sensitive identity and vehicle information, including passports, driver's licenses, and vehicle details. Multiple reports on November 4, 2025 described the rollout and raised questions about the security implications of keeping such data in the browser.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
4 references tracked. Mallory keeps watching after this page renders.
malwarebytes.com
Open sourcezdnet.com
Open sourcetechrepublic.com
Open sourcehackread.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 has introduced new layered security defenses in Chrome to address the growing risks of indirect prompt injection attacks and account takeovers, particularly as the browser integrates more agentic AI capabilities. Key features include the User Alignment Critic, which independently evaluates and vetoes potentially malicious actions by Chrome's AI agent, and Agent Origin Sets, which restrict the agent's data access to only relevant or user-approved sources. These measures are designed to prevent attackers from exploiting untrusted web content to hijack user sessions or exfiltrate sensitive data, and to mitigate site isolation bypasses that could compromise user privacy and security. In parallel, Google has acknowledged a surge in account takeover incidents targeting Chrome users, where attackers steal credentials, authentication codes, and session cookies to access synchronized data stored in the cloud. The company is urging users to strengthen their authentication methods and reconsider the use of browser-based password managers, as a single compromised account can expose a wide range of personal information. Google is also rolling out additional protections for Workspace accounts to counteract these threats and safeguard user data across its ecosystem.
Jun 29, 2026
Google has made **Device Bound Session Credentials (DBSC)** generally available in Chrome, rolling it out for Google Workspace customers, Workspace Individual subscribers, and personal Google accounts to blunt account takeovers driven by stolen session cookies. The feature cryptographically binds a session cookie to the device where authentication occurred, using hardware-backed protections such as the **Trusted Platform Module** on Windows and **Secure Enclave** support on macOS, so exfiltrated cookies cannot be replayed on another machine to bypass MFA. Google said DBSC is enabled by default for Workspace customers, integrates with **Context-Aware Access** for device-aware policy decisions, and exposes binding events in audit logs to help administrators monitor session integrity. The move follows sustained abuse of stolen Google authentication artifacts by infostealers and adversaries leveraging mechanisms such as the undocumented OAuth **MultiLogin** API, with operators tied to **Lumma** and **Rhadamanthys** claiming they could restore expired cookies. At the same time, researchers at Phishu disclosed **VaultJacking**, a phishing technique that can steal an entire Google Password Manager vault after capturing a victim’s 6-digit PIN, then registering an attacker-controlled device to sync passwords and passkeys without malware or prior device compromise. Phishu said the attack sidesteps DBSC because it does not rely on replaying stolen cookies, underscoring that Google’s new protection sharply reduces pass-the-cookie risk but does not stop credential- and PIN-based phishing against synced account data.
Jun 29, 2026
Google has embedded its Gemini AI assistant directly into Chrome, marking the browser's largest update to date. The integration introduces features such as AI-powered page summarization, scam detection, smarter notifications, and one-click password resets. Gemini in Chrome is opt-in, with staged availability starting in the US for desktop users, and includes enhanced safeguards and privacy controls.
Jun 29, 2026