Urgent.News

What's breaking now, across thousands of outlets.

Tech

12TB of Steam Files Leak as a Decade’s Worth of First- and Third-Party Game Data Is Exposed

Data includes both completed and unfinished game builds published on Steam between 2003 and 2013.

12TB of Steam Files Leak as a Decade’s Worth of First- and Third-Party Game Data Is Exposed

An estimated 12 terabytes of data from Steam has been leaked, encompassing a decade's worth of game information published on the platform between 2003 and 2013. According to content creator Gabe Follower, the leaked data was obtained through a publicly accessible endpoint, and the extraction process did not involve any hacking. Valve shifted to a new storage system in 2013, which explains why the data set ends at that point.

The 12TB of data includes every game on the Steam library from 2003 to 2013, not just Valve-developed titles. This massive collection contains full games, beta versions, and even early prototype versions that were uploaded to Steam during the 10-year period. Some of the discovered information includes a pre-release build of Left 4 Dead with altered HUD, voice lines not present in the final release, and changed sections of the game map.

As archivists, enthusiasts, and others explore the leaked data, it is likely that additional information will be unearthed. At present, Valve has not addressed the data leak.

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

Read the original at ign.com →

More in Tech

The Gate That Stayed Silent — When a Blocker Count That Drops Reads as Improvement

In the last article , I argued that the safety contract should move out of the LLM critic and into deterministic gates. The critic can vary. The gates should hold.

  • Blocker counts on structural categories appeared as improvement, masking real issues
  • Silent gate failure mode discovered, gates stop firing after refactor unnoticed
  • Proposed gate canary: deterministic health check before every evaluation sweep

How to Build Node.js Failure Metrics Dashboards and Email Alerts for SaaS

Short answer: emit one custom counter for each operational failure, put those counters on a small dashboard, and have a Node.js job poll short windows for threshold breaches before handing…

  • Emit custom counter for each operational failure in Node.js
  • Use Node.js job to poll for threshold breaches before sending alerts
  • Include idempotency key in metric payload to prevent double-counting

More from Monday 31 August →