Loading story…
Google has rolled out end-to-end encryption (E2EE) for Gmail on Android and iOS, extending a capability that had previously been limited to the web for eligible Google Workspace customers. The feature lets enterprise users compose and read encrypted email directly in the Gmail mobile app, with messages encrypted on the sender’s device and decrypted only on the recipient’s device so that Google cannot access message contents in plaintext on its servers.
The mobile rollout is available to organizations using Google Workspace Enterprise Plus with Assured Controls or Assured Controls Plus, after enablement by Workspace administrators and users. Google said the update is intended to reduce dependence on third-party encryption tools and secure portals, particularly in regulated industries such as healthcare, finance, and defense-related contracting. The service is built on Google Workspace client-side encryption, which keeps encryption keys under customer control outside Google infrastructure and supports compliance needs including data sovereignty, HIPAA, and export controls; recipients outside Gmail or without the Gmail mobile app can access encrypted messages through a web browser.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Google announced that Gmail end-to-end encryption is now available in the Gmail app on Android and iOS for eligible Google Workspace enterprise users. The feature lets users compose and read encrypted emails natively on mobile, with administrator enablement and licensing requirements.
Google started rolling out a new Gmail end-to-end encryption beta model for enterprise users, further evolving its encrypted email offering.
Google added support for sending encrypted Gmail messages across platforms, allowing encrypted email delivery beyond same-platform usage.
Google broadened availability of Gmail client-side encryption beyond its initial beta phase, extending access for eligible Workspace customers on the web.
Google introduced Gmail client-side encryption in beta for web users, marking the initial rollout of encrypted Gmail capabilities for enterprise environments.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
Apple and Google have begun rolling out **end-to-end encrypted** Rich Communication Services (**RCS**) messaging for cross-platform chats between iPhone and Android users, bringing stronger privacy protections to a protocol intended to replace traditional SMS. The beta rollout applies to iPhones running **iOS 26.5** on supported carriers and Android devices using the latest **Google Messages**, with encryption enabled by default and expanding over time to new and existing RCS conversations. The feature is based on **GSMA RCS Universal Profile 3.0** and uses the **Messaging Layer Security (`MLS`)** protocol, which is designed to prevent Apple, Google, and carriers from reading message contents while they are in transit. Availability still depends on carrier support and updated client software, so encrypted RCS will not reach all users immediately, and privacy advocates noted that metadata may still be exposed and cloud backups may remain unencrypted unless users enable additional protections such as Apple **Advanced Data Protection**.
Jul 22, 2026
Apple released an *iOS/iPadOS 26.4 developer beta* that adds **end-to-end encryption (E2EE) for RCS messaging** in limited testing, with availability constrained by device/carrier support and currently limited to **Apple-to-Apple** RCS conversations. The implementation is tied to upgrading to **RCS Universal Profile 3.0** built on the **Messaging Layer Security (MLS)** protocol, aligning with the GSMA’s prior move to standardize E2EE for RCS. The beta also expands platform hardening by allowing apps to opt into the full protections of **Memory Integrity Enforcement (MIE)** (beyond the previously available “Soft Mode”), and reporting indicates Apple may enable **Stolen Device Protection** by default in this release line. Google released the first *Android 17 beta* with multiple privacy/security changes aimed at tightening network and cryptographic defaults and improving user control. Android 17 **deprecates** the `android:usesCleartextTraffic` manifest attribute; apps targeting Android 17+ that set `usesCleartextTraffic="true"` without a **Network Security Configuration** will have cleartext traffic blocked by default, pushing developers toward more granular policy via configuration files. The beta also introduces a public **HPKE (Hybrid Public Key Encryption)** Service Provider Interface, adds user preference controls for **VoIP call history integration**, and expands **Wi‑Fi ranging** for proximity detection and secure peer-to-peer discovery.
Jun 29, 2026
Google has launched a new security feature for Gmail and Google accounts that allows users to designate trusted friends or family members as recovery contacts. This feature is designed to help users regain access to their accounts if they are locked out, for example, due to forgotten passwords, lost passkey devices, or account compromise. Users can select up to 10 trusted contacts, who must accept the request to serve in this role. When a user is locked out, they can initiate the recovery process, which involves sharing a code with their chosen contact. The contact receives a notification and must verify the request by selecting the correct code from a set of options, ensuring that only genuine requests are honored. This process uses number-matching authentication to reduce the risk of social engineering attacks. Google recommends that users choose contacts who are likely to respond quickly, as the recovery request expires after 15 minutes. The company also advises selecting individuals with strong cybersecurity awareness to minimize the risk of exploitation by attackers. The trusted contacts feature is part of Google’s broader push towards passkeys as the future of account authentication, addressing the challenge of device loss that can leave users unable to access their accounts. The recovery process is designed to be secure, with the contact unable to access the user’s account directly, but able to verify the user’s identity. Google Messages will also alert users to spam and help keep texts private, further enhancing account security. The setup process for recovery contacts is straightforward and can be completed on both desktop and mobile devices via the Google account security settings. This new method provides an additional layer of resilience for account recovery, supplementing existing options like email and SMS. The feature aims to reduce the frustration and risk associated with being locked out of critical accounts, especially as more users transition to passwordless authentication. Google’s approach balances convenience with security, leveraging personal trust relationships while maintaining technical safeguards. The company acknowledges that, while unlikely, sophisticated attackers could attempt to exploit the process, so user vigilance remains important. Overall, the trusted contacts feature represents a significant enhancement to Google’s account recovery options, providing users with more reliable and secure ways to regain access to their accounts.
Jun 29, 2026