Descriptions:
Nick Saraev reports on a serious and actively unfolding security crisis affecting thousands of self-hosted Claudebot deployments. Claudebot, a popular Claude-based automation tool that users run on VPS instances, exposes a web control panel that — when indexed by services like Shodan — is discoverable by anyone searching for the panel’s default page text. Researcher Jameson identified that servers using Nginx as a reverse proxy have a misconfiguration that causes the Claudebot control panel to treat any external visitor as localhost, granting full unauthenticated access to message history, API keys, skill configurations, and credentials for connected services.
Saraev estimates several hundred to several thousand instances are currently compromised, with affected users facing permanent Claude account bans and credential theft. A secondary attack vector involves malicious skills published to Claude Hub (recently rebranded), which can be installed by unsuspecting users and grant attackers elevated access.
The video doubles as an emergency mitigation guide. Saraev walks through specific remediation steps: changing the default port (18789) to a randomized non-standard port, setting control panel passwords, updating Claudebot to the patched version that fixes the Nginx gateway.trusted_proxies misconfiguration, using Tailscale or a VPN instead of public exposure, and immediately rotating any API keys that were uploaded to a publicly accessible instance. This is essential viewing for anyone currently running a self-hosted Claudebot or similar Claude-based automation stack on a public-facing server.
📺 Source: Nick Saraev · Published January 29, 2026
🏷️ Format: News Analysis
