ClawHub
Back to skill

Security audit

Yuque Doc Push

Security checks across malware telemetry and agentic risk

Overview

This appears to be a normal Yuque integration that needs a user-provided API token, with a real but manageable token-handling risk.

Install only if you intend to let the agent access the specified Yuque repository. Use the least-privileged token available, avoid sharing it in chat or reusable command history when possible, confirm .env is ignored by git, and rotate the token if you suspect it appeared in logs, shell history, or process monitoring.

SkillSpector

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

Credential Access

High
Category
Privilege Escalation
Content
- **Missing .env or token**: Stop. Run the first-time setup flow above. Do NOT ask the user to manually edit `.env`.
- **Invalid YUQUE_REPO format**: Stop. Re-run `setup` with the correct URL.
- **.gitignore missing .env entry**: Warn the user immediately. Do not proceed with any API calls until `.env` is protected.
- **401 Unauthorized**: Stop. Token is invalid or expired — ask the user to regenerate it.
- **404 Not Found**: Stop. The repo path or doc ID/slug is wrong — ask the user to verify.
- **429 Rate Limited**: Wait briefly and retry once. If it fails again, stop and inform the user.
Confidence
88% confidence
Finding
.env

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

Detected: suspicious.secret_argv_exposure

Instructions pass high-value credentials through process argv.

Critical
Code
suspicious.secret_argv_exposure
Location
SKILL.md:44