---
title: "Leak Ledger: Sealed court files and a Qualcomm memo leaked, week of October 19"
description: "A judge's email to about 140 people, a Qualcomm layoff memo, unreleased Eminem songs and a top-secret leak charge. What each says about tracing a copy."
date: 2026-10-25T12:00:00-04:00
author: "Whistler"
category: "Company news"
series: "Leak Ledger"
tags: [leaks, insider-threat]
url: https://etchv.com/blog/leak-ledger-2026-10-25
---
Leak Ledger is our weekly roundup of leaked documents, images and video. Five leaks this week, most from people with access to the material, and only some of them traceable.

<Roundup>
  <Item headline="Qualcomm's layoff memo reaches Reuters within a day" date="2026-10-20" source="https://www.cnbc.com/2026/10/20/qualcomm-performance-focused-layoffs-reuters.html" sourceName="CNBC">
    Staff heard on Monday that worldwide, performance-based cuts are coming, and Reuters was quoting the chief executive's memo by Tuesday morning. A memo to staff will get out. Sent as an attachment watermarked for each employee, the copy a reporter holds points to one person; quoted or retyped text points to no one.
  </Item>
  <Item headline="A federal judge emails sealed court papers to about 140 people" date="2026-10-20" source="https://www.ca5.uscourts.gov/docs/d04660f6-6422-4403-8c8c-2a7c95679b28/10.20.2026.Special%20Committee%20Order.05.26.90196.pdf" sourceName="Fifth Circuit Judicial Council">
    Refusing to take part in a misconduct inquiry, Judge Ada E. Brown sent judges, lawyers and reporters confidential papers from her case and sealed papers from two attorney-discipline matters the committee says appear unrelated, according to a Fifth Circuit special committee order. For sealed files, a copy watermarked for each person cleared to read them points to whose copy got out.
  </Item>
  <Item headline="Secret recording of Peter Thiel's closed lecture reaches Politico" date="2026-10-21" source="https://www.politico.com/news/2026/10/21/peter-thiel-trump-iran-war-01131284" sourceName="Politico">
    Politico obtained a recording of a closed lecture Thiel gave in Nashville on October 12, in which he said the U.S. should not have gone to war with Iran. Nothing that was handed out leaked, and no watermark reaches a recording someone makes themselves.
  </Item>
  <Item headline="Former Eminem studio employee pleads guilty to selling unreleased songs" date="2026-10-22" source="https://www.cbsnews.com/detroit/news/former-eminem-employee-pleads-guilty-selling-unreleased-music/" sourceName="CBS News">
    The man who helped run the studio's storage pleaded guilty to criminal copyright infringement; prosecutors say he copied 10 or more tracks from its password-protected drives and sold them for about $50,000. A password says who could get in, not who made a copy. We don't watermark audio, so this is a leak our watermark wouldn't have traced.
  </Item>
  <Item headline="Contractor charged with leaking top-secret information to a Substack writer" date="2026-10-23" source="https://www.justice.gov/opa/pr/us-government-contractor-arrested-allegedly-leaking-national-defense-information" sourceName="U.S. Department of Justice">
    The Justice Department says a developer with a Top Secret clearance passed national defense information to a writer he was close to; he is charged by complaint and presumed innocent. The complaint cites access records and phone logs. A watermark wouldn't have helped: prosecutors say what reached her articles was information relayed and rewritten, not a copy of a report.
  </Item>
</Roundup>

## Why it matters

None of this week's leaks needed a hack. A company memo, sealed court files, studio tracks and classified reports each sat with people who had access to them, and a closed lecture was secretly recorded.

Access records say who could have taken a file. They can't say whose copy turned up. When each recipient gets a copy with its own invisible watermark, [detection](/docs/api/detect) reads the unique forensic ID from the leaked file, and you match it to the recipient you recorded. That covers documents, images and video. It doesn't cover audio, retyped or relayed text, or a recording someone makes themselves, and it doesn't stop a leak. Our [guide to invisible watermarking](/resources/invisible-watermarking) covers where it works and where it doesn't.