ClawHub
Back to skill

Security audit

canonry

Security checks across malware telemetry and agentic risk

Overview

This Canonry skill requests broad local and third-party marketing access, but the artifacts disclose the access and consistently require operator control for sensitive actions.

Install only if you intend to run Canonry locally and connect these marketing/business accounts. Protect ~/.canonry/config.yaml with restrictive permissions, avoid sharing it in logs or backups, prefer scoped/read-only keys where possible, and review each requested mutation, schedule, live provider read, or WordPress/ads action before approving it.

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 (1)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The document instructs operators to persist a Google OAuth client secret and user refresh tokens in `~/.canonry/config.yaml` but does not warn that this file becomes a high-value credential store. If local file permissions are weak, backups are shared, or the workstation is compromised, an attacker could recover long-lived secrets and obtain `business.manage` access to managed Business Profiles and associated project integrations.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.