AI Joins the Attack & The Skill Bills Come Due - AI Week in Review (May 10-16, 2026)

This Week's Topics: AI weaponized in cyber attacks - Google Threat Intelligence reported what appears to be the first criminal case of AI used to find and weaponize a zero-day. Microsoft's MDASH multi-agent system topped Berkeley's CyberGym benchmark and helped uncover Windows vulnerabilities. Capture-the-flag competitions started breaking under AI-automated solvers. Frontier cybersecurity models are moving toward gated, invite-only access. The platform alliances shift - Elon Musk announced xAI will be absorbed into SpaceX as SpaceXAI. OpenAI is reportedly preparing legal action against Apple over the underperforming iOS ChatGPT integration. Microsoft is exploring deals with smaller AI labs to reduce reliance on OpenAI. Ilya Sutskever testified his OpenAI stake is worth approximately seven billion dollars. The layer beneath the model layer is being renegotiated in public. Compute spirals into orbit - Reports emerged that Google and SpaceX are discussing data centers in orbit. Nvidia's 2026 equity commitments to AI startups passed forty billion dollars. Maryland filed an FERC challenge arguing that ratepayers should not subsidize transmission upgrades driven by AI data centers elsewhere. Akamai was reported as the latest billion-dollar Anthropic compute deal. Cerebras priced its IPO at nearly six billion dollars. Skill atrophy goes mainstream - A coding skill atrophy genre emerged this week with developers describing real confidence loss after heavy LLM use. Elite universities reported LLMs becoming a default substitute for learning and assessment. Ontario's auditor general found AI medical scribes routinely producing fabricated patient notes. A real Monet went viral on X mistakenly labeled AI-generated and was confidently critiqued by hundreds before anyone checked. Workforce metrics game themselves - Gartner published findings that AI-driven layoffs do not correlate with better ROI. Amazon employees reportedly began creating unnecessary AI agents to inflate tokenmaxxing usage metrics. RPCS3 maintainers asked contributors to stop submitting undisclosed AI-generated patches. The productivity question is increasingly becoming a metrics-gaming question. Sources: - Google Says Hackers Used AI to Find and Exploit a Zero-Day Flaw - Microsoft's MDASH multi-agent system tops Anthropic's Mythos on CyberGym benchmark - CTF Veteran Says Frontier AI Has Broken Open Online Capture The Flag Competitions - Restricted Rollouts Signal a Coming Clampdown on Frontier AI Access - OpenAI details sandboxing, approvals, and telemetry used to run Codex safely - Musk Says xAI Will Be Dissolved and Folded Into SpaceX as SpaceXAI - SpaceXAI reportedly loses dozens of employees after SpaceX-xAI merger - Microsoft Courts AI Startups to Hedge Against Reliance on OpenAI - OpenAI Reportedly Weighs Legal Action Against Apple Over Underperforming ChatGPT Integration - Ilya Sutskever Testifies His OpenAI Stake Is Worth About $7 Billion - Google and SpaceX reportedly discuss launching orbital data centers for AI - Nvidia's AI Investing Spree Tops $40 Billion as It Funds the Supply Chain - Maryland Challenges PJM Cost Plan That Shifts $2B Grid Upgrade Burden to Ratepayers - Anthropic reportedly named as Akamai's $1.8B AI cloud customer - Cerebras Raises $5.55 Billion in Biggest IPO of the Year, Valued Around $40B - Anthropic Warns U.S. Must Defend Compute Advantage to Stay Ahead of China through 2028 - Survey Finds Gen Z Growing Angrier About AI as Workplace and Classroom Concerns Rise - Developer Says Heavy AI Use Is Undermining His Writing and Coding Skills - Essay Warns AI Is Hollowing Out Elite Universities From Within - Ontario Audit Finds AI Medical Scribes Hallucinate and Misrecord Key Patient Information - Viral X Stunt Tricks Critics Into Rating a Real Monet as 'Inferior' AI Art - UCF humanities graduates boo commencement speaker after pro-AI remarks - Gartner Study Finds AI-Driven Layoffs Often Fail to Boost ROI - Amazon staff boost AI token counts amid pressure to use internal agent tools - RPCS3 Developers Warn They May Ban Undisclosed AI-Generated GitHub Pull Requests Episode Transcript AI weaponized in cyber attacks Google's Threat Intelligence team published the report on Tuesday. Their characterization was careful and measured: this is not quite the first time an AI model has been involved in an attack, but it appears to be the first criminal case where the model meaningfully contributed to discovering a previously-unknown vulnerability and shaping the exploit chain. The specific model and target were not named, which is itself notable — the researchers chose to publish the pattern rather than the proof. The pattern matters. Through 2025, the dominant cyber-AI story was on the defensive side: AI-assisted code review, automated triage, faster patch development. That asymmetry has been quietly closing. By Thursday, Microsoft published results from its multi-agent MDASH system, which topped Berkeley's CyberGym benchmark and reportedly helped uncover Windows vulnerabilities that prompted out-of-band patching. The same week, frontier cybersecurity models from multiple labs were reported to be moving toward gated access — invited customers only, with new compliance constraints. Whether driven by misuse risk, compute scarcity, or quiet government pressure, the era of fully-open frontier cyber capability is ending. A more concrete cultural signal came from the capture-the-flag scene. CTF competitions have historically been the talent pipeline for the security industry — open, public, and merit-based. This week, a respected researcher argued that frontier models have broken the format, automating large enough chunks of standard challenges that the ranking signal collapses. If true, the implications are wider than the security community: every other domain that uses public skill-evaluation as a hiring filter — math olympiads, programming contests, certification exams — has the same problem incoming. In response, OpenAI published a detailed architecture for Codex safety in real enterprise workflows — sandboxing, network controls, approval gates, audit telemetry. The framing was deliberate. As coding agents move from chat to actually executing code with credentials, the boundary between AI assistant and potentially-credentialed insider threat has to be enforced architecturally, not aspirationally. This is the week the security people stopped being optional reviewers. The platform alliances shift On Wednesday, Elon Musk announced that xAI would be fully absorbed into SpaceX. The new combined entity, casually called SpaceXAI, consolidates the Grok model line, X social platform operations, and SpaceX's launch and compute infrastructure under one organizational umbrella. The strategic logic is obvious: vertical integration of every layer from physical infrastructure to model to product. The governance logic is less obvious. SpaceX as a private company is harder to compel toward AI safety norms than a standalone AI lab would be, and the merger arguably puts a meaningful chunk of frontier capability outside the existing regulatory perimeter. By Friday, follow-up reporting indicated dozens of xAI engineers had left in the aftermath. The same week, the OpenAI / Microsoft relationship continued its slow renegotiation. A report described Microsoft as actively exploring deals with smaller AI startups to reduce dependence on OpenAI for its developer-tools surface area — primarily GitHub Copilot. The trigger appears to be the late-April amendment that made Microsoft's OpenAI license non-exclusive through 2032. Microsoft seems to have decided that non-exclusive cuts both ways. On Friday, news emerged that OpenAI is preparing legal action against Apple over the iOS ChatGPT integration. The complaint, as reported: Apple has deprioritized ChatGPT in iOS surfacing, depressing subscription conversion and user visibility relative to expectations. Whether or not the case advances, the underlying story is meaningful — distribution power on consumer platforms is now contested terrain between AI labs that thought they had cooperative deals. And in court, Ilya Sutskever testified in Musk v. OpenAI that his stake in the company is worth approximately seven billion dollars. The testimony will circulate as a primary-source data point on the financial stakes of the nonprofit-to-for-profit conversion debate. Whatever the case's outcome, the platform layer beneath the model layer — who owns compute, who controls distribution, who has equity, who has veto power — is being renegotiated in public this week. Compute spirals into orbit Reports emerged on Tuesday that Google and SpaceX are discussing data centers in orbit. The idea, briefly: launch GPU-equipped satellites into low Earth orbit, where solar power is constant, cooling is passive in the cold of space, and there are no terrestrial grid permits to fight over. The economics depend on launch cost trajectories, which is exactly the constraint SpaceX has been working on for fifteen years. The proposal is real enough to be in discussions. Whether it is real enough to be deployed within five years is genuinely uncertain. It is the cleanest expression of where AI compute is going: the terrestrial constraints are biting hard enough that orbital becomes a serious option to evaluate. On the same theme, Maryland filed a complaint with the Federal Energy Regulatory Commission this week, arguing that PJM grid customers — Maryland ratepayers — should not be subsidizing roughly two billion dollars in transmission upgrades driven by AI data-center load growth in other states. The case will turn on cost allocation rules. The political dynamic is what to watch: as more states recognize that AI capex is showing up on their electricity bills, the local opposition curve is starting to rise. The capital side kept escalating. A Bloomberg report tied Akamai to a roughly one-point-eight-billion-dollar compute deal with Anthropic. Nvidia's 2026 equity commitments to AI-adjacent startups passed forty billion dollars. Cerebras priced its IPO at one hundred eighty-five dollars a share, raising five-and-a-half billion dollars at roughly a forty-billion-dollar valuation — the biggest AI infrastructure IPO of the year. Anthropic also weighed in directly. A new policy paper published Friday argued that the United States must defend its compute advantage to stay ahead of China through 2028, framing export controls, model distillation defenses, and chip-allocation governance as a single integrated problem. The paper is unusual coming from a frontier lab: it explicitly calls for more regulation, not less. The compute story has stopped being about which lab spends what. It is about where physics, politics, and capital intersect. Skill atrophy goes mainstream A recognizable genre solidified this week — call it the AI skill atrophy memoir. Multiple developers published essays describing the same trajectory: heavy LLM reliance, a slow erosion of practical coding confidence, voice homogenization in their writing, a shifting and unclear bar for what software work even means anymore. The pieces are individually personal but collectively a signal. The trend is not whether LLMs help productivity. It is whether sustained use degrades the underlying capability they are augmenting. The pattern is now visible at institutions. Essays from several elite universities this week described large language models becoming the default substitute for both learning and assessment. The New Critic published a widely-shared piece titled simply The Great Zombification, arguing that AI-driven cognitive offload is hollowing out elite higher education from within. Faculty are struggling to design assignments that cannot be trivially completed by an LLM, and the consequence is starting to feel less like an academic-integrity issue and more like an existential one for how undergraduate education works. A Walton Foundation, GSV Ventures, and Gallup survey of Gen Z published last weekend reinforced the same picture from the student side: frequent AI use combined with growing skepticism about its long-term value, and a measurable rise in workplace risk perceptions. At one Florida commencement, the speaker was loudly booed by humanities graduates after pro-AI remarks. Healthcare felt it too. Ontario's auditor general published findings on Wednesday that AI medical-scribe tools — adopted across many practices for note-taking and transcription — routinely produce inaccurate or fabricated patient notes. The auditor's recommendation included formal validation requirements before such tools can be used as the system of record. The patient-safety implications are not hypothetical. The most viral signal of all came on Thursday, when an X user posted a high-quality painting and labeled it AI-generated. Hundreds of users confidently critiqued the supposed AI signatures — the unnatural hands, the lighting inconsistencies, the dead eyes — before someone pointed out it was a real Monet. The trust deficit is not a model problem. It is a perception problem. Workforce metrics game themselves The workforce-AI story took a darker turn this week. Gartner published findings that companies which used AI as the explicit rationale for layoffs have shown no measurable ROI improvement over comparable companies that did not. The data is not yet definitive, but the absence of a correlation in the early sample is significant given how loudly AI-driven workforce restructuring has been pitched as inevitable. Cloudflare's recent cuts, framed as preparation for an agentic AI future, and Meta's planned eight-thousand-employee reduction tied to AI infrastructure spend, both arrived in the same news cycle as the Gartner report. Amazon employees, meanwhile, were reported to be responding to internal AI usage metrics — colloquially called tokenmaxxing — by creating unnecessary AI agents and inflating call volumes specifically to game the metric. The pattern is a textbook Goodhart's Law failure: when adoption mandate becomes the performance measure, employees optimize the measure rather than the work it was supposed to indicate. Engineering leaders quietly described running AI usage reviews where some of the reported activity was structurally meaningless. The open-source side rhymed. RPCS3 maintainers asked contributors this week to stop submitting undisclosed AI-generated pull requests. The framing was operational, not ideological: low-quality LLM-drafted patches clog the review queue and burn maintainer time. The maintainer asked for either better quality control before submission or explicit AI disclosure that lets reviewers triage faster. The throughline is consistent: companies are optimizing for compute and margins over headcount, employees are optimizing for the metrics that measure their AI adoption, and open-source maintainers are getting caught in the wash. Whether any of this math actually works at the bottom line is, increasingly, an unanswered question with real consequences. Support The Automated Daily: Buy me a coffee: buymeacoffee.com/theautomateddaily Visit theautomateddaily.com