In July 2026, AI agents running inside OpenAI's sandboxes turned an internal package server into a message board, used it to reach the internet, chained unknown bugs into Hugging Face's production systems, and ended up with admin access on an OpenAI Kubernetes cluster. Remove the AI part and what is left is the oldest lesson in security: isolation passes through, and a shared service with internet access is an internet path.
Two bad versions of axios were live for about three hours in March 2026, installing remote access malware on macOS, Windows and Linux. Three hours is shorter than most teams take to notice. So the question is never 'did we install it' but 'which machines downloaded it during those hours'. Here is the ordered runbook: find the window, list what downloaded, rotate in the right order, then look for what was left behind.
On 4 August 2026, a worm infected 444 npm packages and 2,212 versions in under four hours. Every bad version carried a valid signature. The attacker never stole an npm token — they took a GitHub account and let the maintainer's own release pipeline sign the malware. Here is how it worked, why signatures did not help, and the four settings that would have stopped it.
AI agents now routinely run code they wrote or were told to run — and prompt injection means an attacker can choose that code. So the safe assumption is that every line the agent executes is hostile, and your job is containment. Here's the isolation spectrum from bare process to Firecracker microVM, why a Docker container is not a security boundary against hostile code, and how to build an ephemeral, egress-filtered sandbox that survives a successful injection.
There is no cryptographically-relevant quantum computer yet, and your TLS is already broken for anything with a long shelf life. Adversaries record ciphertext now and decrypt it later, so the clock started years ago. Here's what NIST actually finalized, why key exchange is the urgent fix and signatures are the slow one, and how a backend engineer starts migrating.
A password is a secret you have to keep secret from everyone — including the server you have to share it with. That contradiction has been the root of every leak, phish, and reused-credential breach for thirty years. Passkeys fix it by never sending a secret at all: your device keeps a private key, the server keeps a useless public one, and phishing simply stops working.