Highprofile stalking / harassment cases
Shively, Kentucky (2026) – Officer Asad Zahir allegedly ran 2,048 Flock searches on two vehicles tied to his child’s mother over ~5 months; 241 searches occurred while a protection order was active. Charged with official misconduct and unlawful computer access.

Fort Pierce, Florida (2025–26) – Former officer Josepher Crutchfield searched a woman’s plate 189 times in 8 months via Flock; she later filed a stalking protection order. Charged with felony unauthorized computer access.

Richmond County, Georgia (2023–25) – Deputy Jose Ferrer searched a single tag at least 1,146 times, entering reasons like “SUSPICIOUS” and “BOB.” Arrested for ALPR misuse and oath violations.

Milwaukee, Wisconsin (2025–26) – Officer Josue Ayala used Flock to learn his partner’s location 124 times and her ex’s 55 times; pleaded guilty to attempted misconduct. Weeks later, the internalaffairs detective investigating him, Tehrangi Chapman, was arrested for his own Flock/GPS stalking.

Amarillo, Texas (2026) – Former officer Christian Eder faces 78 misdemeanor counts for running a romantic rival’s plate 76 times with fake reasons.

San Jose, California (2026) – SJPD fired an officer who abused Flock to help his cousin track a woman who had accused the cousin of domestic violence; cited by advocates as a third CA ALPRstalking case.

Bibb County, Georgia (2026) – Three former sheriff’s deputies (Toni Lewis, Coznavian Stubbs, Joseph Callaway) arrested for using Flock to stalk people with whom they had personal relationships; charged with stalking and prohibited licenseplate data use.

Katy, Texas (2024–25) – Former officer Sergio Guadalupe Rodriguez indicted for using Flock (and a tracking device) to stalk his exwife over several months; charged with stalking and misuse of official information.

Orange City, Florida (2024) – Former officer Jarmarus Brown arrested for searching his exgirlfriend’s plates 100+ times and sharing vehicle videos via his agency laptop.

Albany County, New York (2026) – Sheriff’s investigator accused of spying on nearly halfadozen people, including an exgirlfriend, via Flock over ~2 years; faced criminal charges.

New Bedford, Massachusetts (2026) – Officer accused of tracking an exgirlfriend via Flock; department temporarily shut its ALPR network after audit showed “a concerning number of times” her plate was searched.

Sarasota, Florida (2026) – Officer Cory Waiters fired and arrested after 335 Flock searches of his expartner’s car; charged with computer misuse and official misconduct.

Lufkin, Texas (2026) – Officer Klein arrested after allegedly tracking seven plates, one of them over 3,400 times; department suspended Flock use.

Braintree, Massachusetts (2024–26) – Former detective Mark Sherrick charged with criminal harassment for using police tools including Flock, GPS, and databases to monitor his exgirlfriend for months.

Other documented misuse patterns
Nationwide tally (2026) – A Washington Post/USA TODAYcited investigation identified at least 50 officers charged or accused of unauthorized ALPR surveillance; 46 of those cases involved Flock. About half were ex/partner stalking cases.

Institute for Justice database – Catalogs 200+ ALPR abuse incidents, including domestic stalking, wrongful stops, and nonlawenforcement uses; Flock features heavily in recent officermisuse cases.

Immigration enforcement – ACLU notes ICE/CBP repeatedly used Flock to pursue immigrants without warrants, raising separate civilrights concerns beyond individual officer stalking.

Wrongful stops / escalations – Reports include a Colorado case where an officer wrongly accused a woman of theft based on a Flock hit and ignored exonerating evidence, and a mother and children held at gunpoint after an ALPR false “stolen” flag.

Also an embarrassing fact - access to those systems, via hacked computers of not-very-tech-savvy GOVT workers, who have expensive EDR, which obviously did little to protect them, when they self sabotaged themselves by falling for baits such as fake audio driver updates, other clickfix style attacks or installed a RAT without knowing they did so.
A hefty treasure trove of Flock data is already on sale on the so called "dark web".

Ah yes, the classic Windows gaming experience: shelling out for high-end hardware, keeping your system fully updated, and then watching your favorite games immediately self-destruct because your glowing mousepad dared to talk to the kernel.

Who could have predicted that a piece of flashing rainbow plastic would be the ultimate DRM to stop The Finals from launching? Truly, brilliant engineering.
When your operating system is so fragile that a driver named after inpoutx64 gets stage fright from RGB LEDs, you really start to wonder if the entire Windows kernel is just held together by duct tape, corporate prayers, and ancient legacy code from 1998.
Forget cyber threats - the real apex predator of modern PC gaming isn't ransomware; it's Microsoft's monthly patch cycle turning your rig into an expensive RGB nightlight that can't actually run video games.
Let's face it Ransomware - would not exist, if Windows didn't exist.

So, the fraudsters set up TWO separate lookalike domains—surfsidebeach[.]org (adding an 's' to the town) and a typo-squatted domain adding an extra 'i' to Wildcat Contractors, just to sit in the middle and play puppet master.

Which leaves three incredible options: either the scammers simply scraped public contract records, or someone's system was hacked for months of comms snooping and thread-sniping, or an insider was feeding details. Take your pick, because literally none of those scenarios make anyone involved look competent.
And the best part? Nobody figured out $545,000 of public money went off a cliff until six weeks later, when the actual contractor called up asking why their invoice was overdue, only to be told, "Wait, we thought we already paid you?"
Truly a masterclass in government financial controls. Nothing says "peak enterprise security" quite like transferring half a million in taxpayer funds based on an unverified email thread and a copy-pasted signature.

Most domain registrars have a SLAs or OLAa suggesting turnaround time of about 24 - 72 hours when it comes to malware or phishing abuse

In contrast GoDaddy takes forever for enforcement even for trivial cases, and with proof handed over on a silver platter.
I wonder why GoDaddy are so vocal about this, perhaps because they may lose a significant chunk of their so caller customer or reseller base, because lets face it:
If Jhon Doe who always pays with cryptocurrencies has had 1280 domains revoked for confirmed fraud so far, chances are, well the 2181st one shall not be of very high quality either, wink wink.
However pivoting in such a manner is something GoDaddy seems incapable of doing, same as writing a regular expression for countless easy to predict DGA
domains following the same pattern.

In their "arsenal" of tools for efficient stalling is also requesting a subpoena or court order (?!), e.g. fighting digital crime with analog means.

Some GoDaddy staff also do not seem completely aware of their obligations as a registrar entity, specifically section 3.18 of the RAA, as they are quick to dodge responsibility in many cases with "we are just the domain registrar" excuse, which is complete nonsense.

Critical vulnerabilities in July’s Patch Tuesday
There are many critical vulnerabilities, so we’ll highlight only the most urgent ones. In our list, the CVSS score never drops below 9.6.
CVE-2026-57092 (CVSS 9.9) — EoP in VMSwitch, allows escape from an isolated environment with full host compromise. A use-after-free vulnerability that allows a low-privileged attacker to cross the virtual machine boundary and gain access to the host. ZDI notes that a similar exploit was demonstrated at Pwn2Own Berlin on ESXi. Hyper-V users need to update VMSwitch today.
CVE-2026-56190 (CVSS 9.8) — RCE in RDP, unauthenticated, network-based, no user interaction required. Those with RDP servers accessible via the internet are at critical risk; such configurations are practically unsustainable in 2026.
CVE-2026-50518 (CVSS 9.8) — RCE in the DHCP server: heap overflow, unauthenticated, network-based. And this isn’t the only problem with the DHCP server. In this release, it also contains CVE-2026-50370, -56159, and -48564, while the DHCP client contains CVE-2026-54128.
CVE-2026-50522 and CVE-2026-58644 (both CVSS 9.8) — a pair of RCE vulnerabilities in SharePoint servers: deserialization of untrusted data, unauthenticated, and without user interaction. Although Microsoft describes the exploit’s reliability as “unproven”, this is, to put it mildly, untrue. For CVE-2026-50522, a working exploit was demonstrated at Pwn2Own Berlin. In the same group is CVE-2026-55040 (CVSS 9.1), an authentication bypass discovered by Rapid7 experts. Exploiting this vulnerability is the first link in the attack chain; the second is currently under embargo and will be disclosed (and patched) in August Patch Tuesday. Together, they enable RCE without authentication. Meanwhile, the July Patch Tuesday marks the end of support for SharePoint Server 2016 and 2019.
CVE-2026-56188 (CVSS 9.8) — RCE in the Windows Server network driver. The exploitation is highly complex (TOCTOU), but if successful, this vulnerability allows privileged code to be executed over the network without user interaction — in other words, it enables the creation of network worms.
CVE-2026-55008 (CVSS 9.6) — spoofing in Exchange Server (it’s unclear why this is called spoofing, as the description explicitly states “XSS”). An attacker sends a specially crafted email; the victim simply opens it in OWA — and arbitrary JavaScript is executed in their session.
Seems like malware devs know more about undocumented windows kernel features than the few folk remaining working in Microsoft yet. So using a modern OS - you still get a ton of vulns.
Using an obsolete one - threat actor may simply say "Poor guy still on windows 10" and move on to targets of higher interest - e.g. crypto bros or VCs who also use the same computer to steam play games and sign SAFE transactions on.

Some of macho Hamacho s achievements so far, most of which are borderline legal at best. It is a big club, but you ain’t in it:
Jan. 20, 2025 – Withdrew the U.S. from the Paris Climate Agreement (again). Criticism: Undermines U.S. climate leadership and slows emissions reductions.
2025 – Large-scale federal workforce reductions and agency restructuring. Criticism: Reduced expertise and capacity in public health, science, and environmental enforcement.
July 2025 – Exempted more than 100 industrial facilities from certain pollution-control requirements. Criticism: Could increase exposure to carcinogens and toxic pollutants for nearby communities.
Feb. 5, 2026 – EPA enforcement against polluters fell to a record low. Criticism: Environmental groups argue it weakens accountability and encourages noncompliance.
Feb. 18, 2026 – Administration moved to revoke the legal basis for major U.S. climate regulations. Criticism: Seen as an attempt to dismantle decades of environmental protections.
March 2026 – Executive actions and policy shifts favoring continued glyphosate use and limiting some pesticide liability. Criticism: Public-health advocates argue they prioritize chemical manufacturers over health concerns.
May 19, 2026 – EPA proposed rolling back drinking-water limits for several PFAS ("forever chemicals"). Criticism: Critics say it exposes millions to higher levels of persistent toxic chemicals.
May 2026 – IRS settlement reportedly shielding many of Trump's, his family's, and affiliated businesses' pre-settlement tax returns from future audits. Criticism: Tax experts called it unprecedented and argued it creates unequal treatment under tax law. (Reuters/AP reporting.)
June 2026 – Continued approvals and support for certain PFAS-related pesticide uses. Criticism: Environmental groups argue this increases long-term contamination risks despite health concerns.
July 8, 2026 – FDA rejected a petition to set enforceable PFAS limits in food. Criticism: Public-health advocates argue the decision leaves consumers inadequately protected from "forever chemicals."
This list says plenty alone.

Just 0.1% of accounts on Polymarket take home 67% of the profits - this says plenty on its own.
It is genuinely laughable to see the exact same playbook being recycled for Polymarket that we saw with Pump.fun and GMGN.ai just a few months ago. The industry’s creative well is clearly dry, so they’ve returned to the most bottom-tier marketing tactic imaginable: the "Hey, printing money is easy—why are you still poor?" bait.
Just like with those previous "ecosystems," they are flooding social media with a barrage of manufactured, fake win posts to create a frantic sense of FOMO. It’s the same sleazy script: use paid puppets to LARP as financial geniuses on fake dashboards, all to lure in fresh exit liquidity that will inevitably be dumped on. They aren't building platforms; they are running standardized scams that rely on the same tired, predatory tropes to trick people into funding someone else’s exit.
At this point, if you see a post promising "easy money" on a new "prediction" or "memecoin" platform, you aren't looking at an opportunity—you’re looking at a repeat performance of the same trashy hustle.

The same applies to Polymarket, Kalshi and Opinion trade. All of which are gambling websites, pretending to be "prediction markets", which they are not.

It’s truly impressive watching these "prediction markets" work overtime to rebrand degenerate gambling as high-level financial strategy. As exposed in a reddit thread by WSJ, 0.1% of accounts are vacuuming up 67% of the profits, proving that the only thing being "predicted" here is how quickly the house can drain your wallet.

AWS researchers supposedly found the "jailbreak", meanwhile everybody else (MS, FireEYE (Mandiant) aka Google) missed it, seems somewhat plausible

ah yes. Background fetch. Such a "useful" concept ps1 Nuke New-Item -Path 'HKLM:\Software\Policies\Google' -Name 'Chrome' -Force | Out-Null; New-ItemProperty -Path 'HKLM:\Software\Policies\Google\Chrome' -Name 'BackgroundModeEnabled' -PropertyType DWord -Value 0 -Force | Out-Null; New-Item -Path 'HKLM:\Software\Policies\Microsoft' -Name 'Edge' -Force | Out-Null; New-ItemProperty -Path 'HKLM:\Software\Policies\Microsoft\Edge' -Name 'BackgroundModeEnabled' -PropertyType DWord -Value 0 -Force | Out-Null uBlock ||*/service-worker.js$script,important ||*/sw.js$script,important Chrome/Edge Ctrl+Shift+I Network tab any request Override headers. Permissions-Policy: background-fetch=() Chrome chrome://settings/?search=background Continue running background apps when Google Chrome is closed - toggle to OFF Edge edge://settings/?search=continue

From https://www.revisor.mn.gov/bil...
Prediction markets; hosting prohibited.
A person is guilty of a felony if the person, for consideration and as part of a business:
(1) creates a prediction market;
(2) operates, manages, or controls a platform or system intending that consumers will use the platform or system to make wagers in a prediction market; (3) intentionally facilitates the operation of a prediction market by:
(i) identifying or listing events knowing the events will be used by consumers to make
(ii) accepting, holding, or directing the disposition of money or other things of value for
(iii) determining, administering, or enforcing the terms, pricing, or settlement of wagers
made by consumers;

So does that imply that some folks recently featured in Forbes 30 under 30 are now felons? Interesting what do the "concerned legalizations" think about the about the so called "meme coins" MELANIA and TRUMP and WLFI.
I guess 3.6B embezzlement from cryptobros is fine, but ONLY if you are the POTUS haha.