Early access
Your servers, hand-checked every day.
HandsCheck.ai connects to your Linux servers over SSH, read-only, and looks for signs of compromise: rogue accounts, hidden persistence, web shells, tampered WordPress sites. It tells you what changed since yesterday, explains what it means, and proposes fixes that run only after you approve them.
$ hc check --host web-1
Connecting as handscheck@web-1 (read-only) · Ubuntu 24.04 · 3 sites
✔ system 2 security updates pending · kernel 6.8.0
✔ users no new accounts · sudo intact
✖ persistence new systemd unit since yesterday, not from a package:
dbus-socket-helper.service → /usr/sbin/authd
✖ malware shop.example.com: PHP file in wp-content/uploads/2026/10/
created 02:54 UTC, modified time set back to 2023
! wordpress shop.example.com: new admin "wp-support" (registered date copied from user #1)
✔ exposure no directory listings, no backups in web roots
✔ health p95 response 410 ms · PHP-FPM workers 12/40
3 findings (2 critical, 1 high) · verified · 2 fixes proposed for your approval
Next: hc findings show 1
From the terminal
hc check runs the same checks on demand: during an
incident, after a deploy, or before you hand a server over. Every command can print JSON for your own scripts.
From the browser
Add your servers once and we check them daily. See open findings, what changed, and trends across every server and site, and approve proposed fixes in one place.
What it checks
The server first, then every site on it.
Cheap, repeatable checks collect the facts on every run. AI agents then look at what is new or changed, dig further with read-only commands, and explain what they found in plain language. A second agent verifies a finding before it reaches you.
Server
System
OS and kernel support status, pending security updates, tampered system binaries, unexpected SUID files.
Users and access
New root-level accounts, changes to sudo, new SSH keys, suspicious logins and privilege escalation in auth logs.
Persistence
Systemd units and cron jobs that no package installed, preload tricks, hidden files in temp directories.
Exposure
Open ports, admin tools and info pages left public, directory listings, database backups in web roots.
Logs
Brute-force and credential-stuffing patterns, logins followed by uploads, errors that come right before a web shell.
Health
Response times and errors your visitors actually see, not just resource warnings.
Websites and WordPress
Site discovery
Finds every site on the server from its web server config, so new sites are covered without extra setup.
Malware
Web shells and backdoors, PHP in uploads, obfuscated code, and files whose timestamps were faked to blend in.
WordPress
Core and plugin checksums, known-vulnerable plugins, rogue administrators, and suspicious login sessions.
Why we built it
Built from a real incident.
We run a fleet of web servers hosting many WordPress sites. In the fall of 2026 attackers got in through leaked admin passwords and vulnerable plugins, hid backdoors inside real plugin folders with faked timestamps, and eventually escalated to root and locked us out of sudo.
The signals that finally caught it (new files that are older than they claim, admins that appeared out of nowhere, services no package installed, logins followed within minutes by plugin uploads) are the checks HandsCheck.ai now runs every day.
Get early access
We're onboarding a small number of teams who run their own servers on AWS, DigitalOcean and similar. Leave your email and we'll be in touch.