Homeland Security Lied About Child Porn To Search Activist’s Phone

U.S. Department of Homeland Security seal on American flag
Photo: chrisdorney / Shutterstock

A Homeland Security email said “terrorism” while officers pressed “kiddie porn,” and that split now frames a federal test of power at the border.

Story Snapshot

  • Court-file reporting says agents cited child porn while an internal alert focused on terrorism-linked activism.
  • A named officer reportedly admitted they had no reason to suspect child porn.
  • The traveler denied consent, asked for a lawyer, and then his phone wiped after a code was entered.
  • Prosecutors charged him with destroying evidence; the case spotlights border search rules.

What Records Say Happened At The Airport

Homeland Security Investigations sent an alert to Customs and Border Protection to seize Sam Tunick’s phone, with or without his cooperation, tied to suspected terrorism activities and Stop Cop City activism, according to court-file reporting. At secondary screening, officers asked Tunick if they would find “kiddie porn.” He denied it. Defense filings quoted an officer who acknowledged there was no reason to suspect child pornography, undercutting the stated pretext. Those are hard claims to square.

Defense lawyers say Tunick refused consent and asked to speak with an attorney, while officers replied they did not need a warrant for a border device search. He eventually provided a code. The device, a Google Pixel running GrapheneOS with a duress feature, then went blank and appeared to restart. Reports describe that behavior as consistent with a duress code that erases data instead of unlocking the phone. That moment turned a search dispute into a felony case.

The Charge And The Duress-Code Flashpoint

Federal prosecutors in the Northern District of Georgia charged Tunick with destroying evidence under federal law, pointing to the immediate wipe that followed the entered code. Media accounts summarize the government’s theory this way: Tunick gave a duress password to defeat custody of his data. GrapheneOS documentation and coverage explain that a separate duress code can trigger a full wipe of keys and contents, which matches the described screen behavior in the room. The legal question is not the wipe alone, but intent at that instant.

One detail cuts to credibility. The internal Homeland Security Investigations instruction reportedly keyed on terrorism-linked activism, not child exploitation, and said to take the phone regardless of cooperation. An officer’s reported admission that there was “no reason whatsoever” to suspect child pornography makes the “kiddie porn” line look like a door-opener, not a lead. If a jury hears both, the stronger record favors the defense on pretext. Conservative common sense says tell the truth, especially when the government holds the badge.

Why Border Device Searches Keep Sparking Fights

Border searches of phones and laptops have surged. Courts treat the border differently under the Constitution. The Supreme Court has not set clear rules for how the border-search exception applies to smartphones, and lower courts split over what level of suspicion is needed for basic versus forensic device searches. Congress’s legal summaries also note travelers say they feel coerced to give passwords and fear seizure if they refuse, a pressure point that shows up in case after case. That gray zone invites conflict.

Customs and Border Protection says it can search devices to enforce laws on terrorism, child exploitation, and national security, and that it may detain or seize devices if locked by a passcode. That is real authority. But authority must ride with honesty. If officers waved a child-abuse claim while following a different internal script, that tactic risks losing the room in court and outside it. Americans right and left expect straight dealing. Power is safest when it stays inside both the law and the truth.

What To Watch Next

The case turns on a few sharp questions. First, what the full Homeland Security Investigations email said, who received it, and whether the line agents read it before speaking. Second, whether the interrogation record shows ongoing requests for counsel and clear denials of consent. Third, whether forensic analysis nails down that the entered code was the configured duress credential and not an error. Finally, whether a court accepts the destruction-of-evidence theory for a compelled unlock scenario. One hearing could decide the shape of all four.

Sources:

reason.com, cybernews.com, rawstory.com, techtimes.com, 404media.co, securityboulevard.com, islamicpostonline.com, gadgetreview.com, reddit.com, yahoo.com, ziare.com, dlapiper.com, nacdl.org, congress.gov, harvardlawreview.org

© partiallypolitics.com 2026. All rights reserved.