ClawHub
Back to skill

Security audit

WHOOP Morning

Security checks across malware telemetry and agentic risk

Overview

This WHOOP reporting skill has a plausible purpose, but it asks for persistent health-data credentials while key commands it tells users to run are not included in the reviewed artifact.

Review before installing. Only proceed if you can verify the missing `whoop-auth` and `whoop-morning` executables from a trusted source, are comfortable granting persistent WHOOP OAuth access, protect `~/.clawdbot/.env` and the token cache with owner-only permissions, and route any scheduled reports only to a private destination.

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

Lp3

Medium
Category
MCP Least Privilege
Confidence
84% confidence
Finding
The skill declares required environment variables containing sensitive OAuth material but does not declare any explicit permissions, reducing transparency about its access to secrets. While the behavior appears expected for an OAuth-based integration, missing permission signaling can cause users or platforms to underestimate the sensitivity of the skill.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill instructs the user to store the OAuth client secret and refresh token in a local plaintext-style env file without any explicit warning about protecting that file. If the local account, backups, logs, or file permissions are weak, these credentials could be stolen and used to access the user's WHOOP data or mint further access tokens.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
This code persists OAuth-style tokens to a predictable file under the user's home directory without setting restrictive file permissions or providing any notice that sensitive credentials are being stored locally. If the file is readable by other local users, exposed via backups, or left behind on a shared system, an attacker could reuse the tokens to access the user's WHOOP account data until expiry or refresh.

Session Persistence

Medium
Category
Rogue Agent
Content
## Setup

### 1) Create WHOOP OAuth credentials

You already have:
- `WHOOP_CLIENT_ID`
Confidence
88% confidence
Finding
Create WHOOP OAuth credentials You already have: - `WHOOP_CLIENT_ID` - `WHOOP_CLIENT_SECRET` Store these in `~/.clawdbot/.env`. ### 2) Authorize once (get refresh token) Run: ```bash /home/claw/c

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.