Loading story…
Amazon-owned Ring introduced Ring Verify, a content authenticity feature designed to help recipients determine whether Ring camera videos have been edited or altered after leaving Ring’s cloud. The feature embeds a digital “tamper-evident” seal (content credentials) into videos; edits such as trimming, cropping, applying filters, or even brightness adjustments will cause verification to fail, signaling the file has been modified rather than proving it is “fake.”
Ring Verify is automatically applied to videos recorded from December 2025 onward and is included with videos downloaded or shared from Ring’s cloud across Ring devices, with no user setup required. Verification can be performed by submitting a Ring video link for an immediate result (with Ring stating the link check occurs in-browser and is not uploaded), and Ring advises requesting an original Ring-app share if a file returns “not verified” (e.g., due to pre-launch recordings or third-party platform recompression). Videos recorded with end-to-end encryption are expected to return “not verified,” limiting the feature’s applicability for E2EE users.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
When TechCrunch checked Ring's new verification service, Ring.com/verify was not yet working, and the announcement was reportedly accessible via a direct blog URL but not prominently listed on Ring's blog homepage. TechCrunch said it sought clarification from Ring about the rollout.
Ring announced Ring Verify, a content verification feature designed to help recipients determine whether Ring camera footage has been altered after leaving Ring’s cloud. The feature uses embedded content credentials so edits such as trimming, cropping, brightness changes, filters, or compression can cause verification to fail.
Ring said its Ring Verify authenticity feature would be automatically enabled for videos recorded on Ring devices from December 2025 onward. The capability applies to videos downloaded or shared from Ring’s cloud, while end-to-end encrypted recordings are not compatible and will show as not verified.
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.
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.
Ring has introduced **Throw Away the Key Encryption (TAKE)**, a new default video-encryption architecture designed to retain cloud-based camera and AI features while reducing the period in which Ring can decrypt customer footage. Built on the open Messaging Layer Security (MLS) standard, TAKE assigns unique rotating keys to recordings; Ring can use a temporary cloud-held copy to process requested features, then deletes the key within 24 hours of completing that processing. A phased global rollout is planned to begin in September 2026. Ring said it will be unable to provide TAKE-protected video in response to valid government requests once the relevant keys have been deleted, though it may still supply non-video account information and users can voluntarily share recordings. Customers can instead enable end-to-end encryption, which offers stronger protection but disables Shared User video access and certain cloud-dependent capabilities; keys may be recovered through nearby-camera authentication, passphrases, or cloud backups. Ring Verify, a separate digital seal for validating exported cloud-video integrity, is not compatible with end-to-end-encrypted recordings.
Aug 28, 2026
Apple introduced **Reference Image**, an opt-in provenance feature for the iPhone 18 Pro and iPhone 18 Pro Max that is intended to prove an image originated in an iPhone camera and was not subsequently altered. In Reference mode, the main sensor cryptographically signs pixel data immediately after capture, before software processing; the phone retains a secure digital negative locally and uses Private Cloud Compute to render an unprocessed version for private validation. Apple says it retains hashes rather than reference photographs, does not publicly identify photographers or correlate images from the same sensor, and can revoke compromised photos or sensors if fraud is detected. The feature is designed to help recipients compare a reference image with an edited image and detect manipulation or AI-generated content, but its initial scope is limited to specified iPhone models, regions, and Apple-device viewing. Critics note that Apple has not published the sensor-attestation and cryptographic design for independent review, retains central authority to invalidate provenance data under defined security conditions, and does not use 3D depth information to prevent “photo of a photo” attacks. Apple argues its hardware-based approach offers stronger protection against data injection, OS compromise, hardware tampering, and cryptographic attacks than software-only alternatives.
Sep 16, 2026
Apple introduced **Apple Reference Image**, an opt-in photo-authenticity capability for the iPhone 18 Pro and iPhone 18 Pro Max. In Reference mode, the phones’ new Main camera sensor signs image data at the pixel level during capture; Private Cloud Compute then develops that data into an unalterable reference image intended to serve as a digital negative. The Photos app displays the reference image beside the corresponding photograph, enabling users to compare it against later edits, and APIs for iOS, iPadOS, and macOS 27 will let third-party applications display the reference asset. The feature arrives with Apple’s iPhone 18 Pro lineup, which runs iOS 27 and is scheduled to be available beginning September 18, 2026. Apple plans to add **SynthID** support later in 2026 to help identify AI-generated or AI-edited images. Reference Image will not be available at launch in China, while capture will be unavailable at launch in the EU; EU users can nevertheless develop and view existing reference images on Apple operating systems version 27.
Sep 10, 2026