ClawHub
Back to skill

Security audit

WHOOP

Security checks across malware telemetry and agentic risk

Overview

This WHOOP skill is mostly aligned with its stated purpose, but it asks for long-lived health-account access and tells users to run missing, unreviewed scripts.

Review before installing. Do not enter WHOOP credentials or enable the daily cron unless you can inspect the missing `bin/whoop-auth` and `bin/whoop-morning` code. Treat the refresh token like a password, keep the `.env` and token cache private, avoid sharing command output if it contains tokens or health details, and know how to revoke the WHOOP app authorization.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Rogue AgentSelf-Modification, Session Persistence
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Lp3

Medium
Category
MCP Least Privilege
Confidence
85% confidence
Finding
The skill declares required environment variables containing sensitive OAuth credentials and a refresh token, but the skill metadata does not declare corresponding permissions or clearly surface that it consumes secrets. This creates a transparency and governance gap: users or platforms may run the skill without understanding its access to stored credentials and persistent account access.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The instructions tell the user to place client credentials and a long-lived refresh token into a local .env file, but provide no warning about secret sensitivity, file permissions, accidental check-in, or local compromise risk. Because the refresh token enables ongoing API access and WHOOP rotates tokens, insecure storage can expose persistent account access if the host or file is read by another process or user.

Session Persistence

Medium
Category
Rogue Agent
Content
### What the user does (one-time)

1) Create a WHOOP app and get credentials:
- `WHOOP_CLIENT_ID`
- `WHOOP_CLIENT_SECRET`
Confidence
76% confidence
Finding
Create a WHOOP app and get credentials: - `WHOOP_CLIENT_ID` - `WHOOP_CLIENT_SECRET` 2) In the WHOOP developer dashboard, set Redirect URL: - `https://localhost:3000/callback` 3) Put secrets into `~/

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.