How My Docker Setup Saved Me From a Supply Chain Attack (And Why Yours Should Too)

Versión en español aquí.

It's finally Friday! You leave work and go home to work on your side project (yep, that's me). You open your computer and start working on it by running composer update because you want to keep your dependencies up to date.

Next morning, you wake up to the news that a popular Laravel package you use has been compromised. Attackers injected a credential stealer into 233 versions, ready to exfiltrate your SSH keys, cloud credentials, browser data, crypto wallets—the whole digital enchilada 1. Panic sets in. You check your composer.lock. Your heart skips a beat. You have version 15.29.3 of laravel-lang/lang, one of the compromised versions 2.

Been there? I was, on May 22, 2026.

But here's the plot twist: When I dug deeper, I realized my Dockerized PHP setup had just become my unexpected bodyguard. Let me tell you how running PHP through Docker containers added a security layer I never planned for, and why you should consider it too.