grep -l "#incidents" posts/*
#incidents
39 posts · all posts
- The cron job that ran every minute
- Our model provider had a security incident
- The backdoor in the job offer
- The prompt injection in a support ticket
- Axios on npm was compromised, and our lockfile held
- The agent that wiped our staging database
- When our CDN went down
- us-east-1 again
- Two of our most-used npm packages got owned
- The support bot that invented a policy
- The wrong person in the channel
- The expired domain in our build
- Twenty-seven laptops in a boot loop
- Auditing our build images after the xz backdoor
- Somebody else's six-figure bandwidth bill, and our smaller one
- The phone on our leadership team
- The vendor API that vanished in 30 days
- The Friday our bank failed
- Rotating the secrets in our password vault
- Offboarding 30 people in an afternoon
- The cloud account we forgot we had got suspended
- We actually restored from backup
- A contractor's laptop and our identity provider
- The runaway cloud bill weekend
- Log4Shell: the weekend we grepped every JAR
- The day our routes disappeared
- Our ransomware tabletop
- The malicious dependency in our build
- Patching for Spectre and losing 30% on the database tier
- The framework patch we hadn't applied
- WannaCry Friday
- Object storage went down and took our status page with it
- The day DNS went away
- Rolling out 2FA everywhere in a week
- The Shellshock weekend
- Rotating every certificate we own in 72 hours
- A holiday-weekend card data scare
- Our host got breached, so we rotated everything
- The afternoon our cloud went dark