ClawHub
Back to skill

Security audit

Beautiful PDF

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent PDF-making skill with disclosed local rendering steps; the main caution is its mutable npx install command.

Install from a pinned or otherwise verified source when possible, and do not run the npx install command with elevated privileges. When using the skill, keep private source files and generated page images private, and only process documents you are comfortable passing through Pandoc, WeasyPrint, and PyMuPDF.

A.I.G

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
README.md:19
Finding

Unpinned npm Package Execution Through npx

Content
View full analysis
Remediation
View remediation
add AntreasAntoniou/beautiful-pdf ``` 2. Where the installer supports it, pin the skill source to an immutable commit hash or signed release rather than a mutable repository reference. 3. Document the expected npm publisher, registry, package version, and verification procedure. 4. Prefer a lockfile or another integrity-verification mechanism that records cryptographic package hashes. 5. Review the selected installer package and its transitive dependencies before recommending it. 6. Advise users not to run the installation command with administrative privileges. 7. Consider offering a non-executing installation method, such as downloading and verifying a signed release archive before copying the reviewed files. ]]>

SkillSpector

Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
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 · SECURITY.md (reported line 3)May include surrounding context.

md
# Security

Please report vulnerabilities privately through GitHub's security advisory interface. Do not include credentials, private documents, access tokens, internal hostnames, or personal paths in a public issue.

This project provides agent instructions and local helpers. It is not a sandbox, an authorization system, or a guarantee that an external service is secure.

Rp1

Medium
Category
MCP Rug Pull
Confidence
85% confidence
Finding

The README instructs users to install the skill via npx skills add AntreasAntoniou/beautiful-pdf without pinning a specific version or commit. That means future installs may resolve to different code than was originally reviewed, increasing supply-chain risk if the package or its dependency resolution path is later compromised or unexpectedly changed.

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The starter HTML template sets lang="en", which encodes an English locale directly into the example. Under the policy, forcing a specific language without user opt-in can be a natural-language locale violation, and this guide does not mention that the language should be adjusted based on user context.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.