Latest release: v2026.5.28Download zip
Capabilities
Compatibility
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The package purpose is to connect Synology Chat to OpenClaw for direct messages; the code registers a Synology webhook route, validates tokens, applies sender allowlists and rate limits, and sends replies through the configured Synology incoming webhook.
Instruction Scope
Runtime instructions are limited to channel setup, routing, formatting hints, and security warnings. I did not find hidden prompt overrides, unrelated automation, destructive actions, or behavior outside the channel integration.
Install Mechanism
The artifact is an @openclaw/synology-chat npm-pack from the trusted OpenClaw publisher, source-linked to openclaw/openclaw, with no npm install scripts and only zod as a packaged dependency.
Credentials
The plugin uses expected Synology credentials and configuration such as SYNOLOGY_CHAT_TOKEN, incoming webhook URL, allowed user IDs, rate limit, and optional insecure SSL. Accepting webhook tokens from query parameters is a hardening concern, but it remains tied to the declared webhook-auth purpose.
Persistence & Privilege
When configured, it registers an HTTP webhook route and keeps in-memory rate limit/cache state while the channel is running. It uses OpenClaw session/routing APIs for message delivery, with no evidence of hidden persistence or privilege escalation.
Scan Findings in Context
[SDI-4] expected: Webhook token validation is expected for this channel plugin. The artifact does accept token from body, query string, or headers; query-string token support is weaker operational hygiene, but it is not unrelated credential collection or evidence of malicious behavior.
[SQP-2] expected: Logging inbound message metadata is part of webhook handling, but the code also logs a short message preview with username and user ID. This is a privacy/log-retention hardening issue rather than purpose-mismatched behavior.
[staticScan] expected: The supplied static scan reported clean with no suspicious patterns.
[VirusTotal] expected: VirusTotal telemetry was clean across the supplied engines and does not conflict with the artifact review.
Assessment
Install only if you intend to connect OpenClaw to Synology Chat. Keep the webhook token secret, prefer sending it in the request body or an authorization/custom header rather than a URL, restrict allowed user IDs for production, and review log retention because message previews may appear in application logs.