TYSKShorts: How Coding Error Exposed 80,000 Cameras & National Security | Flock Safety Breach
The short version: A YouTube breakdown (via TYSK, built with AI tools) argues a backend API flaw let outsiders bypass authentication on Flock's 80,000-camera network, exposing real-time location data on millions.
Our Take
Credit to TYSK for packaging a dense technical story into something digestible — even if the video itself admits it was assembled with NotebookLM and Gemini, which means we'd treat the specific numbers and scenarios (Navy SEALs, foreign adversaries, the works) as a dramatized narrative rather than a verified forensic report. We haven't independently confirmed every detail here, and neither should you before you repeat them.
But strip away the AI-narrated flourishes and the underlying structural point survives scrutiny: a nationwide ALPR network built by a single private vendor is, by design, a single point of failure. When one company's misconfigured test server can theoretically become a pipeline into 'live' location data on millions of Americans, that's not a hypothetical bug bounty footnote — it's the entire argument against centralizing this much surveillance infrastructure in one corporate hand in the first place. Flock has had real, documented lapses before; whether this particular story is the sharpest example or an AI-amplified retelling of one, the risk category it's pointing at is genuine.
This is exactly why we keep pushing people to know what's watching their own streets. Check our camera map to see what's near you, and if you want to push back on your city council or police department adopting or renewing a Flock contract, our take-action page has the tools to get started.
This is DeFlock The USA’s original commentary. The video above is the work of TYSKchannel, published on YouTube — full credit to the creator.