// Open-source LPR countermeasure research
Flock Safety is not a camera company. It is a data aggregation platform. Every plate read feeds a centralized private database. This project does not target the cameras. It targets the database — inducing confident misreads that enter as clean data and corrupt pattern-of-life analysis without triggering failure flags.
Case: Mauston, WI — Active
Response Deadline
April 18, 2026
WI Agencies Querying Flock
221
Documented Query — TX Sheriff
"had an abortion,
search for female"
Notice Issued
2026-03-19
01 — The Problem
Municipal governments are deploying Flock Safety cameras without fully understanding what they joined. This is not a local camera network. It is national surveillance infrastructure with ICE access vectors, query justifications logged as a single word, and documented misuse — including criminal charges against a Wisconsin police chief for using the same category of infrastructure for personal purposes.
Your residents' movement patterns — where they go, how often, at what hour — are now a commercial asset on a California corporation's balance sheet. They did not consent to this.
Verona, Wisconsin declined to renew after public pressure. That option remains available to every municipality on the Flock network.
Wisconsin agencies querying Flock
221
Documented query — Texas sheriff
"had an abortion, search for female"
— actual logged justification
Data controller
Private corporation, Atlanta GA. Movement data is a commercial asset on their balance sheet — not yours.
Federal access
Used nationally to assist ICE. Pipeline to federal immigration enforcement upon request.
02 — The Approach
Most LPR countermeasures attack the optical layer — IR flooding, reflective coatings, plate covers. These are cosmetic. They either fail against modern camera tuning or expose users to vehicle code violations.
FlockBlocker targets the database. Flock's commercial value is not any single plate read — it is the aggregated movement history. Pattern-of-life analysis requires data continuity. Corrupt the continuity and the downstream product degrades silently, invisibly, over time.
A failed read gets flagged or discarded — it is a visible gap in the record.
A confident misread enters the database as ground truth.
That distinction is the entire attack surface. The goal is not to defeat the camera. The goal is to make the data worthless to anyone trying to use it downstream — without the system ever knowing it happened.
Research directions include adversarial patch methodologies from published academic literature, OCR character ambiguity exploitation, and retroreflective interference designed to induce systematic misclassification without triggering failure flags. Distribution model: open-source, organic, no coordination required.
03 — Origin
On March 19, 2026, a formal decommission notice was sent to the Mayor, City Administrator, Police Chief, and Sheriff of Mauston, Wisconsin — CC'd to State Senator Sarah Keyeski.
The letter documented Flock Safety's data architecture, the ICE access vector, documented misuse cases nationally and in Wisconsin, and municipal liability exposure under the existing contract. Three specific demands were made: the authorizing ordinance, the full contract including data retention and third-party access terms, and the city's stated position on decommissioning.
A 30-day response window was established. No response becomes documented public record of officials ignoring a formal resident complaint with a sitting state senator CC'd.
FlockBlocker is what gets built while they decide.