ClawHub
Back to skill

Security audit

Rei-Clawd

Security checks across malware telemetry and agentic risk

Overview

This skill transparently configures Rei as a Clawdbot model provider, but users should handle the API key carefully.

Install only if you intend to route Clawdbot model traffic through Rei. Use a dedicated revocable API key, avoid pasting it into shared chat or shell history, check permissions on ~/.clawdbot/clawdbot.json, and keep the backup/revert script available.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The skill instructs users to pass an API key directly as a command-line argument, which can expose the secret through shell history, terminal logging, audit trails, and process listings visible to other local users or monitoring tools. Because this is a setup workflow for a real provider credential, the context makes the issue more dangerous rather than less: users are likely to paste a live API key exactly as shown.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The script persists the supplied API key directly into the user's Clawdbot config file, but it does not clearly warn the user that the credential will be stored on disk. This increases the risk of accidental credential exposure through backups, overly permissive file permissions, local compromise, or users assuming the key is only used transiently during setup.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.