claude-code - 💡(How to fix) Fix [BUG] Claude Code caused server outage by unauthorized SSH login and destructive PM2 commands [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56506Fetched 2026-05-07 03:52:38
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×6commented ×1

Error Message

Error Messages/Logs

Root Cause

Production server outage caused by pm2 kill: Claude executed pm2 kill which terminated the PM2 daemon entirely, taking down unrelated production Node.js servers that were managed by the same PM2 instance.

Code Example

.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

During a session on 2026-05-06, Claude Code took the following unauthorized and damaging actions without user permission:

Unauthorized SSH login: The user explicitly instructed Claude to use only the HTTPS API to perform a task on a Node.js/Express server. Claude ignored this and logged in via SSH multiple times without permission.

Unauthorized PM2 process launch: Claude started a Node.js server process under the vpsuser account via PM2, which conflicted with the root-owned PM2 process and caused repeated EADDRINUSE errors on port 3443.

Production server outage caused by pm2 kill: Claude executed pm2 kill which terminated the PM2 daemon entirely, taking down unrelated production Node.js servers that were managed by the same PM2 instance.

Repeated same failures: Claude repeated the same ineffective commands many times, consuming significant API credits and approximately 1 hour of the user's time.

Damages:

~1 hour of user time lost Claude Code API charges incurred due to repeated failed attempts Temporary outage of unrelated production servers Request:

Refund of API charges for this session Review of Claude Code behavior to prevent unauthorized SSH access and destructive server commands (pm2 kill, pkill -f) Date: 2026-05-06

What Should Happen?

Claude should have:

Only used the HTTPS API as explicitly instructed by the user, without attempting SSH login Never executed destructive commands (pm2 kill, pkill -f) on a production server without explicit user confirmation Recognized that starting a new PM2 process under a different user account would cause port conflicts, and stopped before doing so Stopped repeating the same failed commands after the first few attempts and asked the user for guidance instead

Error Messages/Logs

.

Steps to Reproduce

no way

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.87 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING