BetterSWE DigestWhat is BetterSWE?

News · Issue 8

The GrapheneOS Panic-Wipe Case: When Anti-Forensics Meets Border Search Law

A phone wiped itself at an Atlanta airport. Now the traveler is facing federal charges, and the twist is that a CBP officer typed the code.

A traveler's phone wiping during an airport border inspection

The incident

A phone that erased itself at the border

A traveler's phone wiping during an airport border inspection

In January 2025, Samuel Tunick, an Atlanta activist tied to the movement opposing the city's police training center, landed at Hartsfield-Jackson after a trip to the Dominican Republic. CBP pulled him into secondary inspection and demanded his phone password, and his lawyers say agents skipped Miranda warnings, refused his requests for a lawyer, and told him no warrant was needed.

  1. Jan 2025 (Airport search, phone wipes)
  2. Nov 2025 (Federal indictment filed)
  3. Mar 2026 (Motion to suppress)
  4. Oct 2026+ (Ruling expected)

He gave a passcode. According to the court filing, "the screen went black, flashed several times and the phone appeared to restart". That behavior matches a GrapheneOS duress PIN, an alternate credential that looks like a normal unlock but quietly triggers an irreversible wipe.

The government charged Tunick in November 2025 under a statute covering destruction of property to prevent a lawful government seizure, with a maximum of 5 years in prison. It may be the first prosecution centered specifically on a GrapheneOS duress-PIN wipe.

The mechanism

Two PINs, one of them a kill switch

One PIN unlocks the phone, the other destroys the encryption keys

A duress PIN is a second unlock code you set up in advance. At the lockscreen there is nothing to tell it apart from your real code, no confirmation prompt and no warning. Type the real one and the phone unlocks; type the duress one and it wipes the keys that make the encrypted data readable.

Real PIN

unlocks, data intact

Duress PIN

wipes key material

The wipe targets the key derivation material, so there is no plaintext left to recover. GrapheneOS put it bluntly: "Data cannot be recovered after the key derivation material is reliably wiped. It's not possible and there's nothing we can do to assist with it". The hardware and software are built so that no vendor backdoor can undo it.

The legal twist

Who actually destroyed the evidence?

The causation question: the traveler spoke a code, the officer typed it

Here is the detail the case may turn on: Tunick never typed the code that wiped his phone. He handed over the duress credential as if it were his real password, and the CBP officer entered it. The wipe was set in motion by the officer's own hand.

Defense (compelled disclosure; officer acted)Prosecution (intent to trigger the wipe)

Two readings of the same keystroke

The defense frames it as compelled disclosure, with the destructive act being CBP's independent choice to type an unfamiliar code. The prosecution's theory leans on intent: if you knowingly hand over a credential designed to destroy evidence, your speech is what starts a chain of events you knew would end in a wipe. Whether that counts as the defendant destroying property is genuinely unsettled.

The vendor response

GrapheneOS: you didn't need the duress PIN anyway

Auto-reboot returns the phone to a state where keys are not in memory

Rather than cheer the duress feature, GrapheneOS mostly steered attention elsewhere. Its auto-reboot timer restarts a locked device after a set idle period, dropping it back to the Before First Unlock state where the encryption keys are not resident in memory and cannot be pulled out by forensic tools.

  Unlocked / AFU     keys in RAM   -> extractable
       |
       |  idle reboot timer (e.g. 18h)
       v
  Locked / BFU       keys not loaded -> nothing to extract
Auto-reboot pushes the phone into BFU without touching a duress PIN

The project also points to how far behind extraction vendors sit. A GrapheneOS account citing leaked Cellebrite documents said the newest GrapheneOS release those tools could exploit on a locked device was still from 2022 as of recently. Combined with the default charging-only USB mode when locked, the physical attack surface is thin before anyone reaches for a wipe.

On the duress PIN itself, GrapheneOS urged caution: "People should carefully consider how to use it in an actual duress situation where there can be physical or legal consequences for wiping the device". It defends the feature as legal while nudging users toward protections that don't invite a destruction charge.

The law around it

The border is a Fourth Amendment gray zone

The border search exception and its two search tiers

The border search exception lets CBP inspect travelers and their devices without a warrant or individualized suspicion. CBP's stated position is that "all travelers are obligated to present their electronic devices and the information resident on the device in a condition that allows for the examination of the device and its contents".

Basic search

manual, no suspicion needed

Advanced search

external tools, reasonable suspicion

Tunick's team moved to suppress everything from the interrogation, arguing the search was an unreasonable seizure and that the child-abuse-material pretext masked an investigation into his political activity. Riley v. California required a warrant to search a phone after arrest but never resolved the border context, so lower courts remain split.

Device searches at the border are still rare. In fiscal year 2025, CBP data shows fewer than 0.1% of arriving international travelers had a device searched. Tunick was one of them, and his case now tests whether protecting your own data can itself become a federal crime.

The stakes

Anti-forensics on trial

Why it matters

A security feature that has existed for years is being tested as a crime for the first time, and the outcome will shape how far travelers can go to protect data they are legally allowed to encrypt. The case sits on unsettled ground: whether speaking a duress code counts as destroying evidence, and whether the border search exception survives contact with modern phone encryption. However a court rules, forensic vendors already lag GrapheneOS by years, so the fight is shifting from cracking devices to prosecuting the people who lock them.

The short version

  • Activist Sam Tunick faces a federal charge, up to **5 years**, after a GrapheneOS **duress PIN** wiped his phone during a January 2025 CBP airport search.
  • The case may turn on causation: **Tunick spoke the code, the officer typed it**, raising whether that is destruction of evidence or compelled disclosure.
  • GrapheneOS defends the feature as legal but steers users toward its **auto-reboot to BFU** protection, which blocks extraction without inviting a destruction charge.
  • The **border search exception** still lets CBP inspect devices without a warrant, and courts are split on how far that reaches after Riley v. California.
  • A ruling on the suppression motion isn't expected before late 2026.

Sources

  1. 1.GrapheneOS duress PIN could land a man in prison
  2. 5.GrapheneOS protections against data extraction from locked devices | Hacker News
  3. 7.US citizen charged after GrapheneOS phone wipes during airport search
  4. 9.Border Battle: When Wiping Your Own Phone Is a Crime | U.S. News Decision Points | U.S. News
  5. 10.GrapheneOS Defends Data-Wiping Function That Blocked US Border ...
  6. 12.GrapheneOS protections against data extraction from locked devices - GrapheneOS Discussion Forum