- Can you promise my site won't be hacked?
- No, and be careful with anyone who does. What we promise is the work: updates on a schedule, backups we've actually restored, a person reading alerts, and a written report of what we checked and what we couldn't see.
- My host says PHP is patched. Is that enough?
- Often it is. We still check it from a live page, and ask the host in writing which build is running. On PHP 8.1, 8.0 or 7.4 the version number doesn't change after the patch, so we check the build date: Oct 21, 2026 or later.
- What warning signs do you look for?
- For php2shell, the public ones researchers have shared: a scanner user agent named php2shell-scan, upload requests carrying PHP's upload-progress field, bursts of memory errors, PHP starting programs like wget or curl, a file at /tmp/nfs, new PHP files in the uploads folder, and admin users nobody recognizes. A sign isn't proof. We check before we tell you anything is wrong.
- What happens if you find a real problem?
- We stop and tell you what we found, in plain words, and what we suggest. Cleanup and anything else outside your plan is quoted before we start.
- What's the difference between this and a security plugin?
- A plugin runs inside WordPress. The October PHP flaws sit underneath WordPress, in PHP itself, so a plugin's firewall may not stop them. Wordfence's help pages describe its firewall as running inside WordPress. We work on the PHP, the updates, the backups and the logs.
- Do I need this if my site is on a JKCA care plan?
- Most care plan sites don't. Our care plans host static sites with no PHP, no login page and no database, so php2shell doesn't reach them. We'll confirm it for your site and tell you. Store sites on WooCommerce are different; ask us.
- Do you only work with Seal Beach businesses?
- No. We're in Seal Beach, and the work is remote, so your site can be hosted anywhere.