Urgent.News

What's breaking now, across thousands of outlets.

Tech

A massive Cartoon Network leak exposes decades of behind-the-scenes animation files

A leak of over 200GB of Cartoon Network production files is circulating online. Here’s what’s inside.

A massive Cartoon Network leak exposes decades of behind-the-scenes animation files

A massive leak of behind-the-scenes animation files from Cartoon Network has surfaced online, revealing decades of production files for popular shows like The Amazing World of Gumball, Foster's Home for Imaginary Friends, and The Powerpuff Girls. The leak, which spans over 200GB of material, was traced back to an anonymous X account based in the United States.

In addition to the Google Drive folder containing production files, the leaker shared a master Google Doc with links to even more content from Cartoon Network's extensive back catalog, hosted on a separate file-sharing site. Among the leaked materials are storyboards, pitch documents, model sheets, puppet rigs, and EPS files – all of which offer a rare glimpse into the creation process of professional animations.

While many of these files have since been removed due to copyright violation concerns, the leak has raised questions about the security of production files and the potential impact on artists and studios. This leak arrives on the heels of Skydance's $110 billion acquisition of Warner Bros. Discovery, leading some to speculate about the connection between the two.

Written by urgent.news from Mashable's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at mashable.com →

More in Tech

Vibe Coding Is Quietly Shipping Your API Keys to GitHub

You asked the AI to "just get Stripe webhooks working." Thirty seconds later it did. The code ran, the test payment went through, and you pushed.

  • AI coding assistants leak API keys to GitHub during debugging.
  • Leaked keys can be abused within minutes by automated scrapers.
  • Diffnix tool flags hard-coded secrets and suggests environment variables.

A Small SaaS Release Checklist That Includes the Failure Path

A feature can look finished in a demonstration while still leaving the team uncertain about what happens when a request fails, a permission is missing, or a customer submits the same action twice.

  • Emphasize failure path alongside normal path in release checklist
  • Document expected outcome and failure scenarios for small software change
  • Create scenario table for valid connection, expired credentials, and more

More from Sunday 11 October →