Olvid Channel

• Outcome: Review
• Latest audit: May 28, 2026 at 4:48 AM UTC
• Version:
  0.1.0

Overview

The Olvid chat channel is purpose-aligned, but it needs review because credentials, attachments, and a reconnecting background listener have limited visible safeguards.

Install only if you need Olvid-to-OpenClaw messaging and can use a dedicated, least-privileged Olvid bot key. Protect the daemon, limit which contacts or groups can message the bot, verify where the client key is stored, and be cautious with sensitive attachments until the plugin adds clearer cleanup, retention, and stop controls.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Context-Inappropriate Capability

Medium

• Confidence: 82% confidence
• Finding: The code imports a sensitive client key from OLVID_CLIENT_KEY in the process environment and then may persist it into the plugin configuration. This expands secret-handling behavior beyond simple interactive channel setup and can cause credential exposure if config files are stored insecurely, logged, synced, or inspected later.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: Inbound attachments are automatically written to a fixed directory under /tmp without validation, size limits, retention controls, or any indication of user consent. In a messaging-channel skill, this creates a real privacy and security risk: untrusted remote users can cause potentially sensitive files to be persisted on disk, increasing exposure to disk exhaustion, forensic recovery, cross-process access on shared hosts, and downstream processing of attacker-controlled files.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The onboarding flow collects a client key and saves it directly into the config structure without any user-facing notice that the secret will be persisted. This creates a realistic risk of accidental credential disclosure through plaintext config files, backups, repository commits, workstation compromise, or support bundle sharing.

VirusTotal

66/66 vendors flagged this skill as clean.