Loading story…
CalyxOS released version 8.0, an Android 17-based mobile operating system designed to operate without proprietary Google applications and services. The release supports selected Google Pixel, Fairphone, Motorola Moto G, and SHIFTphone models, adds support for the Pixel 10a, and introduces macOS support in the device-flasher provisioning tool. It also updates microG, Chromium, and Etar.
The platform uses microG to provide compatible implementations of selected Google APIs without installing Google’s proprietary software. CalyxOS pairs this with privacy-oriented substitutes for location, geocoding, application distribution, web browsing, and VPN/Tor connectivity, including services associated with beaconDB and Positon. Organizations deploying privacy-sensitive Android devices should validate application dependencies on Google Play services and test the upgraded operating system and its alternative location and app-distribution components before broad rollout.
See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
CalyxOS 8.0 was released as a privacy-focused Android distribution based on Android 17. The release adds Pixel 10a support, macOS support in device-flasher, and updates microG, Chromium, and Etar.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
6 references tracked. Mallory keeps watching after this page renders.
opennet.me
Open sourceopennet.ru
Open sourcecalyxos.org
Open sourcecalyxos.org
Open sourcepositon.xyz
Open sourcebeacondb.net
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 released **Android 17**, publishing the source code to AOSP under the tag `android-17.0.0_r1` and beginning rollout to supported Pixel devices, with broader availability planned across OEMs including HONOR, Lenovo, OnePlus, OPPO, vivo, Xiaomi, and others. Google also made **Generic System Images** available for `ARM64` and `x86_64`, while the platform adds major usability and device features such as foldable enhancements, App Bubbles, Handoff support, VVC/H.266 video, RAW14, HE-AAC, BLE hearing-aid improvements, and OpenJDK 25 integration. The release introduces a broad set of security and privacy changes, including tighter controls for **contacts**, **location**, and **local network** access, expanded one-time-password handling beyond SMS, stricter restrictions on **dynamic code loading**, stronger lost-device protections, improved threat detection, enhanced **Advanced Protection**, and stricter PIN retry limits. Google also added Certificate Transparency-related enhancements, support for **HPKE** cryptography and **ML-DSA** APK signatures, and continued restrictions on cleartext traffic, alongside Pixel-specific updates delivered through the June Pixel Drop.
Jul 12, 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’s move toward **developer verification** for Android app distribution is drawing criticism from parts of the open-source and alternative app-store ecosystem, including an open letter from the **F-Droid** community and dozens of organizations warning the change could undermine Android’s historically open sideloading and third-party store model. Critics argue verification could make it harder to install apps outside Google-controlled channels—especially in constrained environments (e.g., unreliable connectivity)—and could push some independent developers toward *progressive web apps* or away from Android development entirely; they also note that fully opting out may increasingly require leaving Google-certified Android builds. In parallel, **Motorola** announced a long-term partnership with the **GrapheneOS Foundation** to strengthen smartphone security, citing GrapheneOS’s hardened Android-based architecture (e.g., stronger sandboxing and boundaries intended to reduce exploit impact). The GrapheneOS team publicly noted Motorola devices do not yet meet GrapheneOS hardware requirements and that work is ongoing, and Motorola has not disclosed which specific GrapheneOS features will be integrated; the companies described the effort as joint research and future software/security capability development rather than an immediate product rollout.
Jul 2, 2026