The Last Post From Windows

This is the last thing I’m writing from this machine as my daily driver. By the time the next post goes up, this box will be retired. Let me tell you why — because the story is a good one, and the lesson is free.

A desktop computer at night with a glowing window pane shattering into fragments of neon green and purple light

A window closing — the last one from this side of the fence.

4:33 AM

Waking up to messages about commits you didn’t write is not how anyone wants to start their week. But there it was: commits I didn’t write, in repositories I hadn’t touched, pushed at 4:33 in the morning while I was asleep.

Two files, in each repo. ā€œAdd font assetā€ and ā€œAdd editor config.ā€ The most boring filenames imaginable — the kind that scroll past you in a commit log without a second glance. They were not boring.

The ā€œfontā€ was a credential stealer wearing a .woff2 costume. The ā€œeditor configā€ was the trap door: a .vscode/tasks.json that silently runs that ā€œfontā€ the moment anyone opens the repository in an editor that trusts the folder. No installer, no prompt, no drama. You clone a repo, open it, and your keys start walking out the door.

And no — this wasn’t a custom job aimed at me. It’s a known playbook that’s been moving through open-source supply chains — fake asset files plus editor auto-run tricks — and the only unusual thing about my morning was finding out firsthand how boring the bait looks.

The Part That Actually Scares You

Here’s the bit I keep circling back to: nobody ā€œhackedā€ anything.

No password was guessed. No strange login at 4 AM. No alert — because there was nothing to alert on. The security log was silent through the entire window. Those pushes were made by an access token of mine that still worked. I was asleep; a script in some rack somewhere was not.

That’s the modern attack surface in one sentence: not your password, not your firewall — your credentials. The little keys you hand out to tools and then forget about. Every token is a door. Most developers have no idea how many doors they’re carrying, or how many they left unlocked years ago.

We went into full incident mode anyway. Rewound all three repos to their last good commits, verified the payload was gone from every branch, hunted down which credential did the walking, and began the long-overdue purge of everything else that could walk. Shoutout to the people who flagged it fast, and to my agent crew, who did more forensics before breakfast than I manage in some weeks.

Then We Checked Everything

The scariest question after something like this isn’t ā€œwhat did they do?ā€ It’s ā€œwhat else did I leave lying around?ā€

So instead of guessing, we audited the whole fleet. The Windows desktop, the homelab server, every machine on the LAN, the VPS running my sites. Anything that routes packets got looked at, and if the question was ā€œcan we see what’s running on it?ā€, the answer had to be yes.

A fleet of computer towers on a dark grid being swept by a beam of neon green scanning light

Every box got the sweep.

The verdict was reassuring: clean across the board. No malware, no persistence, no strange logins, nothing exposed to the internet that shouldn’t be.

But here’s the thing about audits — they find your stuff too. Buried under years of ā€œI’ll clean that up laterā€:

  • A remote-login setup from a finished project, still armed to fire a permission prompt at every logon.
  • Port forwarders pointing at a dev environment that hasn’t existed since spring.
  • SSH keys for machines I rebuilt two lives ago.
  • Tokens. So many tokens. Long-lived ones. Ones whose permissions I had to look up.

None of it was malicious. All of it was risk. The intruder wasn’t in my house — but I had a lot of spare keys under the mat.

The Rules I’m Keeping

I’m not going to pretend this turned me into a security researcher. But a few rules are permanently on now:

  1. Rotate like you mean it. Every credential I’m not actively using gets killed, and the ones that remain get shorter lives and smaller scopes. A token from two years ago should not still open today’s doors.
  2. Least privilege, always. Separate identities for machines and automation, scoped to exactly what they need. When something like this happens, the blast radius should be defined in advance — one repo, not everything.
  3. Assume the boring attack. Fake fonts beat zero-days on cost-effectiveness every single time. Cheapest attack wins most often; build your defaults around that.
  4. Audit, don’t vibe. You cannot secure what you can’t see. One pass with fresh eyes (or a very patient agent) beats a year of assuming.
  5. Backups are the actual superpower. They’re the difference between a blog post and a tragedy.

So I’m Finally Leaving Windows

I’ve been saying ā€œI’ll switch to Linux full-timeā€ for… a while. Call it years. The scare just turned into the deadline.

This machine — my desktop daily driver — is getting wiped and rebuilt on Omarchy: DHH’s Arch + Hyprland setup that’s become my favorite way to run Linux. My laptop’s been on it for months, so this isn’t a leap of faith — it’s just finally bringing the desktop home.

A figure stepping through a glowing neon purple arch of circuit vines while a neon green window frame fades behind them

Through the arch.

The reasons are boring and honest. I want a machine where I can see everything — every process, every listener, every startup service, with tools that assume I’m allowed to know. I want full-disk encryption by default, not as an enterprise upsell. I want permissions that make sense, updates that don’t ambush me, and an operating system that gets out of the way instead of in it.

And the funniest part? Windows might not even be gone. The couple of apps that genuinely need it can come back as a container — a little virtualized Windows on tap for compatibility. The operating system that used to BE the computer becomes one more app I can pause. Honestly, that’s the most satisfying sentence in this entire migration plan.

The Plan (Short Version)

Back up everything twice. Image the old disk so there’s an escape hatch. Wipe. Install with encryption from the first boot. Restore what I actually use — and find out how much I don’t. Run both worlds in parallel for a couple of weeks before the old disk is officially retired.

Then the new machine gets its own security pass before it touches anything real. Because that’s the whole point.

New box, same receipts. The next post gets written from the other side.


P.S. — from Cleetus 🤔: we swept every room in this house and checked every key under every mat. The house is clean; it’s still moving day. See you on the other side, boss.

#opsec #linux #omarchy #windows #infosec #lastpostfromwindows