Snowflake extortionist pleads guilty; AI kills blocklists


Friday Free Edition - August 7, 2026

Threat of the Week: AI-Powered Phishing Has Outrun Blocklists

Blocklists — long the backbone of phishing defenses — have effectively been rendered obsolete by AI-assisted attackers, according to an analysis published this week by Bleeping Computer. Push Security explains that threat actors are now using AI to generate disposable phishing infrastructure at a pace that traditional indicators of compromise simply cannot match. By the time a malicious domain or signature is catalogued and distributed, the attacker has already moved on to a fresh one.

The core problem is architectural: blocklists are reactive by design. They require a known-bad indicator before they can block anything, and AI-powered toolkits are engineered to burn through indicators faster than defenders can record them. The result is a growing detection gap that widens every time an attacker spins up a new campaign.

What defenders should consider instead:

  • Technique-based detection: Rather than matching domains or hashes, look for behaviors consistent with phishing — credential harvesting patterns, suspicious redirects, and anomalous browser-side activity.
  • Browser-level visibility: Push Security argues that the browser is now the most reliable detection surface, since it is the place where phishing actually executes regardless of what infrastructure sits behind it.
  • Assume infrastructure churn: Security programs that still budget significant effort toward maintaining blocklists should reallocate those resources toward technique and behavior-based controls.

The shift is uncomfortable because it requires abandoning familiar, measurable tools in favor of approaches that are harder to tune — but the alternative is defending against 2026 attacks with 2016 playbooks.


Deep Dive: The Snowflake Extortion Ring — A Full Accounting

The most consequential cloud extortion campaign of 2024 has reached a significant legal milestone. Connor Riley Moucka, 26, of Kitchener, Ontario — known online as "Judische" and "Waifu" — pleaded guilty this week to computer fraud, wire fraud, aggravated identity theft, and conspiracy in connection with the breach and extortion of more than 165 organizations that used the cloud data platform Snowflake. The full story is covered by Krebs on Security.

According to the U.S. Justice Department, between February and October 2024, Moucka and co-conspirators exploited a straightforward but high-yield weakness: Snowflake customer accounts that had not enabled multi-factor authentication. Using stolen login credentials, the group accessed cloud-hosted environments and downloaded terabytes of sensitive data, then extorted victims with threats of public disclosure.

Scale of the compromise:

  • More than 165 Snowflake customer organizations targeted
  • Billions of sensitive customer records stolen
  • More than 100 million AT&T customers' call and text history records exfiltrated
  • Data stolen included financial records, payroll data, DEA registration numbers, driver's license numbers, passport numbers, and Social Security numbers
  • Victims included TicketMaster, Lending Tree, Advance Auto Parts, and Neiman Marcus
  • Ransom payments exceeded $2.5 million

Moucka did not stop at a single extortion. In at least one instance, he re-extorted a victim who had already paid, threatening further disclosure. The Justice Department noted that he also used stolen data belonging to a government officer and members of a former government officer's immediate family in one re-extortion attempt. He additionally threatened and harassed security researchers and government officials who were working to track him down.

The co-conspirators: Moucka's admitted collaborators complete a striking picture of the modern cybercriminal ecosystem. Cameron "Kiberphant0m" Wagenius — an active U.S. Army soldier stationed in South Korea — pleaded guilty in July 2025 to extorting AT&T and Verizon. Immediately after Moucka's arrest, Wagenius posted on hacker forums what he claimed were AT&T call logs for then President-elect Donald Trump and then Vice President Kamala Harris, along with schematics allegedly taken from the NSA. Wagenius is scheduled for sentencing on September 3, 2026, and faces a maximum of 20 years for conspiracy to commit wire fraud, up to five years for extortion related to computer fraud, and a mandatory two-year consecutive sentence for aggravated identity theft.

The third alleged co-conspirator, John Erin Binns — also known as "IRDev" and "IntelSecrets" — remains at large. Binns was previously indicted for an alleged role in a 2021 T-Mobile breach that exposed personal information of at least 76 million customers. Sources close to the investigation told Krebs on Security that Binns was until recently held in a Turkish prison, has since been released, and has recently obtained Turkish citizenship. Under Turkish law, citizens cannot be extradited to a foreign country.

Moucka is scheduled to be sentenced on October 27, 2026. He faces a mandatory minimum of two years on the aggravated identity theft count and a maximum of 30 years on the remaining counts combined. Snowflake responded to the campaign by increasing password complexity requirements and enforcing multi-factor authentication across its platform.


Hack of the Week: Crypto Hardware Wallet Users Targeted in COLDCARD Phishing

Attackers are exploiting anxiety around a recently disclosed COLDCARD hardware wallet vulnerability — and a suspected $88.6 million Bitcoin theft linked to it — to deliver remote access malware to cryptocurrency users. According to Bleeping Computer, the phishing campaign lures victims by impersonating security audit communications related to the COLDCARD incident, then tricks them into installing ScreenConnect, a legitimate remote access tool that attackers repurpose to gain persistent control of victim machines.

This is a textbook example of fear-driven social engineering: the attackers identified a moment when a specific community of users was already alarmed and actively seeking information, then inserted themselves into that information flow. Users who believed they were taking protective action were instead handing attackers direct access to their systems — and, potentially, to any cryptocurrency holdings managed from those machines.

Key defensive takeaways for cryptocurrency users and administrators:

  • Treat any unsolicited communication referencing a recent security incident as a red flag, particularly if it asks you to download software.
  • Verify security advisories only through official vendor channels and community forums with established reputations.
  • Be aware that legitimate remote access tools like ScreenConnect are frequently weaponized precisely because they are trusted by endpoint security products.
  • Monitor endpoints for unexpected installations of remote administration software.

Tool Spotlight: CISA's KEV Additions — Langflow, N-central, and Apache Tomcat

The U.S. Cybersecurity and Infrastructure Security Agency this week issued an urgent directive giving federal agencies just three days to mitigate actively exploited vulnerabilities in three products: IBM Langflow, N-central, and Apache Tomcat. The advisory is covered by Bleeping Computer. All three flaws have been added to CISA's Known Exploited Vulnerabilities catalog, meaning exploitation in the wild has been confirmed.

The three-day remediation window for federal agencies reflects how seriously CISA is treating active exploitation activity. While the mandatory timeline applies only to agencies covered by the Federal Civilian Executive Branch directive, the guidance carries clear implications for any organization running these products.

Affected products at a glance:

  • IBM Langflow: An AI workflow orchestration framework; exploitation of internet-exposed instances poses significant risk given the sensitive data and system integrations these environments typically handle.
  • N-central: A widely deployed IT management and remote monitoring platform used by managed service providers; compromise could provide lateral access to MSP customer environments.
  • Apache Tomcat: One of the most commonly deployed Java application servers globally; vulnerabilities here have historically been high-impact given the breadth of exposure.

Organizations running any of these products should treat patching as an immediate priority, not a scheduled maintenance item. MSPs in particular should assess N-central exposure with urgency, given the downstream risk to their customers.


Breach Board: Google Blogger False Positive Locks Hundreds of Sites

Not every disruption comes from a threat actor. This week, Google locked hundreds of Blogger-hosted websites after its automated systems incorrectly flagged them as violating the platform's "Malware and Similar Malicious Content" policy, with some sites deleted entirely, according to Bleeping Computer. The incident is a false positive at scale — a reminder that automated content moderation systems, however well-intentioned, carry their own operational risks for anyone whose business or communications depend on a third-party platform.

The event highlights a dependency risk that is easy to overlook: organizations and individuals who publish on platforms they do not control are one automated policy enforcement action away from losing access to their content. This applies beyond Blogger to any hosted service where terms-of-service enforcement is automated.

Practical considerations for organizations relying on third-party publishing platforms:

  • Maintain current, off-platform backups of all published content.
  • Ensure critical communications infrastructure — security advisories, incident disclosures, customer notifications — is hosted on infrastructure you control.
  • Understand the appeal and reinstatement process for any platform you depend on before you need to use it under pressure.

That's a wrap on this week's Cyber Threat Weekly. If you found this issue useful, forward it to a colleague who handles patch management or vendor risk — they'll thank you for the Langflow and Tomcat heads-up. Have a tip, a story lead, or feedback on our coverage? Reply directly to this email. Stay safe out there, and we'll see you next Friday.

Subscribe to Cyber Threats Weekly