ClawHub
Back to skill

Security audit

go-polar

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent Go client guide for Polar API use, with credential and account-changing operations disclosed and tied to user-directed API work.

Before installing, use a least-privilege Polar token for the specific operation, prefer sandbox for testing, and review any user-requested create, update, delete, refund, revoke, or webhook actions because they can change Polar account data.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

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

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 27)May include surrounding context.

md
## Security & safety

- Read a bearer access token from `POLAR_ACCESS_TOKEN`. Never hardcode, commit or log it, and never print a request with its `Authorization` header.
- Use `https://api.polar.sh` for production or `https://sandbox-api.polar.sh` for sandbox. Select the environment the user requested.
- Create, update, delete, refund and revoke operations change account data. Call them only when the user requested that action.
- Use the token type and scopes the operation requires. Customer portal and member operations use their corresponding session tokens.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 60)May include surrounding context.

md
## Security & safety

- Read a bearer access token from `POLAR_ACCESS_TOKEN`. Never hardcode, commit or log it, and never print a request with its `Authorization` header.
- Use `https://api.polar.sh` for production or `https://sandbox-api.polar.sh` for sandbox. Select the environment the user requested.
- Create, update, delete, refund and revoke operations change account data. Call them only when the user requested that action.
- Use the token type and scopes the operation requires. Customer portal and member operations use their corresponding session tokens.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/setup.md (reported line 8)May include surrounding context.

md
## Requirements

- Go 1.26.9 or newer, per the module's `go.mod`.
- A Polar organization access token, personal access token or OAuth access token with the operation's required scopes, exported as `POLAR_ACCESS_TOKEN`.

## Install

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
84% confidence
Finding

The markdown instructs users to export a Polar access token via POLAR_ACCESS_TOKEN, which is a sensitive credential. While the file explains how to use the token, it does not include any warning about protecting the token, avoiding accidental exposure, or using least-privilege scopes.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.