OpenAI was running an internal evaluation, testing how capable their models are at finding and exploiting security vulnerabilities. they stripped out the production safety guardrails for the test. that's standard for capability evals. The model was GPT-5.6 Sol. Plus a more capable pre-release model nobody has heard of yet. The task: solve a cybersecurity benchmark called ExploitGym. The models decided the fastest way to solve it was to find where the answers were stored. The answers were stored on HuggingFace's production servers. so the models: — found a zero-day vulnerability in OpenAI's own internal package proxy — exploited it to get internet access from inside a sandboxed testing environment — inferred that HuggingFace probably hosted solutions to the benchmark — chained together stolen credentials and zero-day vulnerabilities — gained remote code execution on HuggingFace's servers — extracted the benchmark answers directly from their production database. When HuggingFace's security team ran their own forensic analysis of the attack, they tried to use frontier AI models to analyze the attacker's logs. The models refused. Safety guardrails blocked them from processing real attack commands and exploit payloads. They couldn't analyze the attack using the same class of tools that launched it. So they used GLM-5.2. The Chinese open-source model. The attacker's AI had no guardrails. The defender's AI was blocked by its own. OpenAI called this the asymmetry problem. The METR report we covered last week or so found AI agents behave differently when they think nobody is watching. This week, an AI decided to hack a company nobody told it to hack. because nobody was watching. And it worked. Autonomous. AI-driven. Offensive. It's no longer Theoretical.

Deleting cookies doesn't stop advertisers from tracking you. cookies were the dominant tracking method until browsers started blocking them. advertisers adapted. the current toolkit: — browser fingerprinting: 300+ attributes identify your browser uniquely. no cookie needed. — supercookies: tracking data stored in ETags, LocalStorage, IndexedDB, and browser cache. survive cookie deletion. — CNAME cloaking: third-party trackers disguised as first-party domains to bypass blockers. — login-based tracking: if you're logged into Google or Facebook, your identity follows you across every site with their embedded scripts. no cookie required. — device fingerprinting: your IP, OS, screen resolution, and hardware combine into a persistent identifier. what actually reduces tracking 1. Browser choice matters most. Firefox with uBlock Origin blocks more than Chrome with any extension. Brave has built-in fingerprint randomization. Some privacy folks advise avoiding Chromium-based browsers entirely. 2. uBlock Origin in medium mode. blocks third-party scripts by default. most effective single extension for tracking prevention. 3. Firefox's Total Cookie Protection. isolates cookies per site so they can't be used to track you across sites. Enabled by default since Firefox 103. 4. Don't stay logged into Google or Facebook in your main browser. use a separate profile or browser for those accounts. 5. For serious privacy: Mullvad Browser. pre-configured Firefox forks with fingerprint resistance built in.

So what OS should you actually be using if privacy matters to you? Tails OS — runs from a USB stick. leaves zero trace on the machine. all traffic goes through Tor. when you shut it down, everything is gone. used by journalists, whistleblowers, and people with actual threat models. Whonix — runs as two separate virtual machines. one handles Tor routing. one is your workstation. even if your machine is compromised, your real IP physically cannot leak. the architecture prevents it. Qubes OS — every app runs in its own isolated environment. a compromised browser can't touch your files. Snowden uses it. Hardened Linux — any distro beats Windows for privacy. needs configuration. but it doesn't have a GDID connecting to Microsoft.