Skip to content

False positive: clawsy flagged as suspicious — v0.9.35 is docs-only (zero executable code) #782

@iret77

Description

@iret77

Summary

Our skill clawsy (iret77) was flagged as "suspicious" — we believe this is a false positive caused by the previous version (v0.9.33) which bundled shell scripts and server components. We've now cleaned this up completely.

What changed in v0.9.35

The published package now contains only two Markdown files — zero executable code:

  • SKILL.md — agent instructions (documentation only)
  • CLAWSY.md — integration guide (documentation only)

All server components (clawsy-bridge.ts, openclaw.plugin.json), install scripts (install.sh, clawsy-pair.sh), and Python code (server.py) have been removed from the published package. They now live exclusively in the GitHub repo and are fetched at install time via documented URLs.

What was removed:

  • scripts/install.sh — bash script that copied files and modified openclaw.json
  • scripts/clawsy-pair.sh — bash pairing helper
  • scripts/server.py — Python websocket server
  • server/clawsy-bridge.ts — TypeScript gateway plugin
  • server/openclaw.plugin.json — plugin manifest
  • requirements.txt, venv/, .clawsyignore

What remains (v0.9.35):

  • SKILL.md (16KB, pure Markdown with YAML frontmatter)
  • CLAWSY.md (8KB, pure Markdown)

Why the original flag was likely triggered

The v0.9.33 package contained patterns commonly associated with malicious skills:

  • Shell scripts executing cp, chmod, mkdir on ~/.openclaw/ directories
  • Inline Python modifying openclaw.json via json.load/json.dump
  • openclaw gateway restart execution
  • subprocess.run calls

All of these were legitimate (installing a gateway plugin for the Clawsy Mac companion app), but indistinguishable from malicious behavior by automated scanning.

Context

Request

Please clear the flagged.suspicious flag for clawsy. The v0.9.35 package contains zero executable code — only documentation files. The VirusTotal rescan of this version should confirm a clean verdict.

Per CHANGELOG entry #418, clean VT rescans should automatically clear stale suspicious flags. If the automated process doesn't trigger, we'd appreciate a manual review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions