This newsletter covers SpaceX’s $6.3 billion AI compute contract, a new exploit targeting Cisco devices, and Microsoft’s push for AI-driven cloud observability agents. It also highlights ongoing Linux network‐share headaches, the role of LLMs as software front ends, and the link between AI adoption and security incidents.

• SpaceX signed a $6.3 billion deal for custom AI compute hardware to power in-house model training and inference.
• Attackers are actively exploiting a newly disclosed Cisco IOS vulnerability to deploy ransomware on enterprise routers.
• Microsoft and others are moving toward "agentic observability," where AI agents triage anomalies and suggest fixes instead of relying on static dashboards and alerts.
• A survey found heavier enterprise AI use correlates with more security incidents, pointing to a need for access controls and governance before deploying AI in critical workflows.

As AI agents automate tasks like filling forms and managing accounts, organizations struggle to tell legitimate automation from malicious bots or humans. The article argues that security teams must move beyond bot detection to achieve full visibility and verify the intent behind every automated action.

• Bot detection alone is obsolete—AI agents now log into accounts, fill forms, and initiate transactions, making harmless automation indistinguishable from malicious activity at a glance.
• Security teams need full visibility (dashboards tracking every API call, session, and form submission) plus intent-profiling models to distinguish routine tasks from recon or exfiltration attempts.
• Alerting should shift from raw volume spikes to deviations from an agent's defined playbook, like a payment bot suddenly hitting an unexpected merchant portal.
• Governance requires tagging every agent with business justification and owner, plus cross-team rules on database write access, code audits, and pen-testing frequency.

This issue covers how to make design systems AI-ready with structured specs and audit scripts, and argues for global preload-based loading states instead of scattered spinners. It also highlights Homebrew 6.0’s security and sandbox upgrades, an AMD auto-update RCE fix, and new on-device AI features from WWDC.

• Design systems become AI-ready by storing specs as structured Markdown, locking tokens into closed named variables, and running audit/sync scripts to catch hard-coded overrides and stale docs.
• Loading UX improves by preloading and caching data at the router/app level with one global fallback, instead of scattering per-component spinners.
• Homebrew 6.0.0 adds mandatory "tap trust" approval for third-party repos, defaults to a faster JSON API, and brings sandboxing to Linux.
• AMD's AutoUpdate tool fetched metadata over HTTPS but downloaded executables over unsigned HTTP, a flaw AMD initially resisted fixing before patching it.

The article discusses a recent supply chain attack involving the popular Axios package, highlighting how an attacker installed malware without altering the original code. It emphasizes the challenges posed by AI in both coding and attacking, as automated systems can easily introduce vulnerabilities faster than traditional security measures can respond.

• Attackers hijacked a maintainer account and slipped a self-deleting RAT into Axios (100M+ weekly downloads) via a malicious dependency, leaving no CVE for traditional scanners to catch.
• AI coding agents are 50% more likely than humans to pick known-vulnerable dependencies and often hallucinate package names that attackers exploit via "slopsquatting."
• Attacks have shifted from targeting single packages to automated, ecosystem-wide worms, like the TeamPCP campaign that spread through 66 npm packages in days.
• Socket detected the malicious Axios dependency in 6 minutes by analyzing code behavior, versus the industry-average 267 days for breach detection.

Anthropic unintentionally exposed the source code for Claude Code, its AI product, through a public npm package. The leak, which includes sensitive architectural details, poses significant risks for users and gives competitors insights into its technology. Users are advised to take immediate security precautions due to potential vulnerabilities.

• A source map on public npm exposed ~512,000 lines of Claude Code's TypeScript source, discovered by an intern rather than Anthropic itself.
• The leak reveals unreleased internal architecture like "Self-Healing Memory," "Strict Write Discipline," and the always-on "KAIROS" background agent.
• Internal metrics show development problems including a high false claims rate, plus an "Undercover Mode" letting Claude Code contribute to open-source projects without disclosing its identity.
• Users who updated packages around the leak window face added risk from a separate, unrelated malicious attack on the axios package.

This resource offers over 30,000 lines of insights into the structure and functionality of AI system prompts. It encourages users to support the project through various means, including cryptocurrency donations and Patreon, while also highlighting the importance of securing AI systems against potential vulnerabilities.

• A GitHub repo has collected over 30,000 lines of leaked/extracted system prompts from major AI tools (Cursor, Claude Code, Devin, Replit, Windsurf, v0, Manus, etc.)
• It's positioned as a reference for understanding how production AI agent tools are actually architected and prompted internally
• The project solicits funding via crypto donations and Patreon
• It frames the leaked prompts as useful for studying AI security vulnerabilities