❌

Reading view

Snowflake attacker pleads guilty to hack of 165 companies’ data

A Canadian hacker has admitted being part of a group responsible for several major cyberattacks. Connor Riley Moucka pleaded guilty to being part of a coterie of hackers that hit 165 organizations, resulting in the theft of customer records and the extortion of millions of dollars.

Industry sources have identified Moucka as one of the main players in attacks on data hosted by cloud data warehouse Snowflake. Companies affected by the hacks include the likes of AT&T, Ticketmaster and the Neiman Marcus Group.

He worked with two other hackers: John Edward Binns and Cameron John Wagenius. Binns was not in US custody as of April 2026, while Wagenius, going by the name of Kiberphant0m, was arrested in January 2025 and pleaded guilty in July that year

Moucka and other members of the group used stolen login credentials to compromise data belonging to at least 165 customers of a US-based software-as-a-service company. This unauthorized access was used to steal billions of sensitive customer records and download terabytes of information,

β€œConnor Moucka hacked over 150 companies and organizations, obtained extremely sensitive information, and extorted the victims for millions of dollars. Today’s guilty plea serves as a reminder to all cybercriminals, regardless of where they live, that they cannot hide behind a wall of anonymity. You will be found and brought to justice,” said assistant attorney general A. Tysen Duva of the Justice Department’s Criminal Division

The trial is the result of a coordinated worldwide action against the Snowflake group. The investigation was led by the FBI but benefited from contributions from the Royal Canadian Mounted Police, the Australian Federal Police, Spain’s Guardia Civil, the Security Service of Ukraine and the Turkish National Police.

This article first appeared on CSO.

  •  

New Databricks tool uses AI agents to rewrite legacy SQL at scale

Databricks is adding an agentic code conversion capability to its Lakebridge toolkit, using Genie Code to provide its new customers another way to move from rival data warehouses to itsΒ lakehouse built atop Databricks SQL.

The new capability, called the agentic code converter, uses AI subagents to analyze source code, convert files in parallel, validate the translated SQL, and iteratively retry failed sections within a migration project, while allowing developers to define reusable migration rules for enterprise-specific SQL constructs.

The Lakebridge migration tooling already includes multiple transpilation engines, including the pattern-based BladeBridge technology Databricks acquired in 2025, the compiler-based Morpheus, and the LLM-powered Switch transpiler.

The key difference between the transpilers and the new agentic code converter, according to analysts, lies in how each of them executes conversion and how that could benefit enterprises.

β€œDeterministic transpilers (Morpheus) handle syntax mapping well: date functions, join syntax, straightforward pattern-to-pattern translation. They get brittle fast on anything requiring control-flow reasoning, cursors, dynamic SQL assembled at runtime, recursive CTEs implemented differently across T-SQL, Teradata, and Oracle,” said Amit Chandak, chief analytics officer at IT consulting firm Kanerika.

β€œThat’s the same 10% to 15% of a legacy codebase that eats most of the manual remediation time on every migration I’ve worked on,” Chandak noted.

In contrast, agentic code conversion, said Pareekh Jain, principal analyst at Pareekh Consulting, is better suited for stored procedures, dynamic SQL, proprietary functions, and complex business logic that require contextual understanding.

β€œIt should improve first-pass conversion quality and reduce manual remediation, especially for the most complex portions of a migration,” Jain noted.

For CIOs, that translates into shorter timelines and lower costs to complete migration projects, especially those that involve thousands of SQL scripts, Jain added.

Chandak, however, said enterprises should temper expectations, mostly because the agentic code converter capability continues to be in beta.

The current beta limits conversion jobs to batches of 300 files, meaning migrations involving thousands of stored procedures still require multiple runs and manual checkpoints, Chandak pointed out.

That limitation could be somewhat offset by the new custom migration skills feature, included with the capability, which allows developers to codify one-off fixes as reusable conversion rules, although whether the agentic system can perform consistently remains an open question till the product matures, Chandak added.

Even if the capability delivers on that promise, Chandak further pointed out that enterprises should not expect it to dramatically shorten end-to-end migration projects because SQL conversion is only one part of the overall modernization effort, as enterprises still need to reconcile migrated data against production systems, sequence dependencies, and obtain business sign-off before workloads can be cut over.

β€œBecause Databricks’ roadmap places data migration and reconciliation in a future phase, the new capability is likely to compress the SQL rewrite effort rather than the overall migration timeline,” Chandak noted.

Databricks isn’t the only data platform vendor using AI to lower the barriers to migration.

RivalΒ Snowflake already has a similar tool, named SnowCovert, that uses agents to help enterprises move their data, data warehouses, business intelligence (BI) reports, and code to Snowflake’s platform.

Google Cloud, too, enables automated migration workflow through Gemini-powered schema and code conversion capabilities in its Database Migration Service.

  •  
❌