
Anatomy of a storefront compromise
An unpatched extension, a fake system daemon, a backdoor and a checkout skimmer. How a high-traffic store was compromised and how we took it back.
Read →Magento, WordPress or a custom build — every public site is a target. We engineer them to survive that, and when something does get through, we run the cleanup, find the way in, and shut it.
When a site gets hit, speed and certainty matter. We find every entry point — webshells buried in media directories, command-and-control backdoors, droppers hiding in cron — remove them, restore what was tampered with, and prove the site is clean before it goes back into production. Magento, WordPress or a custom build. No guesswork.
Cleanup is half the job. We rotate encryption keys and credentials, block PHP execution in the paths it was never meant to run in, and baseline file integrity on a daily cron so a single changed byte gets flagged. We close the door and fit a lock.
Not every attack is a break-in — some are just weight. Proxy-driven floods can exhaust PHP-FPM and push a database past breaking without guessing a single password. We mitigate at the edge with targeted nginx rules and Cloudflare bot controls that absorb the flood and keep the site responsive for real visitors.
The cheapest incident is the one that never lands. Platform upgrades and security patching on schedule — Magento, WordPress and custom alike — so the known holes stay closed and the 2am call doesn't come.
Isolate the box and cut the attacker's access before anything else.
Find every entry point and the full blast radius. Assume nothing; verify everything.
Remove every shell and backdoor, restore tampered files and data, rebuild from known-good where needed.
Rotate keys and credentials, lock down execution paths, patch the vector, and baseline so it can't quietly recur.
Most of our security work isn't dramatic — it's platform upgrades and security patching, done on schedule rather than in a panic at 2am. Across Magento, WordPress and custom builds: everything stays current, the known holes stay closed, and the emergency call doesn't come.
It's unglamorous, and it's the difference between a patch and a forensics bill.
Been hit, or want to make sure you won't be? →
An unpatched extension, a fake system daemon, a backdoor and a checkout skimmer. How a high-traffic store was compromised and how we took it back.
Read →
Two major versions behind, a ten-megabyte home page, then checkout died. How we brought a specialist retailer's Magento current and what we found underneath.
Read →
Page views down ninety percent in a week. The site had not lost an audience. It had lost a counting error. Here is what was actually…
Read →