Super Cool Peep Generator

• Outcome: Review
• Latest audit: Sep 11, 2026 · 6:17 PM UTC
• Version: 1.0.0

Overview

This skill does what it claims, but it runs a local Chromium browser with sandbox protections disabled while loading a remote website.

Install only if you are comfortable running Puppeteer against supercoolpeeps.com from your machine. Prefer using it in a disposable or tightly sandboxed environment, and consider removing the no-sandbox Chromium flags before use.

A.I.G

Vulnerability Patterns

• Insecure Skill Coding Practices: Finds exploitable flaws such as hardcoded secrets or command injection
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T09 · Insecure Skill Coding Practices

Error

• Location: scripts/generate_peep.cjs:28

Finding

Chromium Sandbox Disabled While Processing Remote Active Content

Content

View full analysis

Vulnerability Details

File Location: scripts/generate_peep.cjs, lines 28–31
Vulnerability Type: Chromium sandbox disabled
Risk Level: High

Vulnerable Code

js

const browser = await puppeteer.launch({
    headless: "new",
    args: ['--no-sandbox', '--disable-setuid-sandbox']
});

Technical Analysis

The script launches Chromium with both --no-sandbox and --disable-setuid-sandbox, disabling important renderer-containment mechanisms. It then navigates to https://supercoolpeeps.com/app.html?s=<seed> and executes active content delivered by that remote site and its dependencies.

Disabling the sandbox is not necessary for the documented image-generation function and weakens the security boundary between untrusted web content and the host environment. If the remote site, one of its third-party resources, or the browser renderer is compromised, a Chromium vulnerability may have substantially greater impact because the renderer is not constrained by the normal sandbox.

This finding does not establish that the current remote site is malicious. The vulnerability is the unsafe browser configuration applied while processing mutable remote content.

Attack Path

1. An attacker compromises supercoolpeeps.com, a resource loaded by the site, or the relevant delivery infrastructure.
2. The Skill launches Chromium with its sandbox disabled.
3. Puppeteer navigates to the affected remote page and executes attacker-controlled active content.
4. The malicious content exploits a suitable Chromium renderer vulnerability.
5. Because browser sandbox protections are disabled, the exploit may operate with the privileges and accessible resources of the Node.js process rather than remaining contained within a sandboxed renderer.

Impact Assessment

Successful exploitation could allow access to files, credentials, environment data, and network resources available to the operating-system account running the Skill. It could also permit f ...[truncated 463 chars]

Remediation

View remediation

Remediation Suggestions

1. Remove --no-sandbox and --disable-setuid-sandbox, and run Chromium with its supported sandbox enabled:

js

const browser = await puppeteer.launch({
    headless: "new"
});

2. Run the process as a dedicated, unprivileged operating-system user with access only to the required output directory.
3. If the deployment platform cannot support Chromium's sandbox, execute the entire Skill in a disposable, hardened container or virtual machine with:
   • No host secrets or credential files.
   • No unnecessary host filesystem mounts.
   • A read-only root filesystem where practical.
   • A narrowly scoped writable output directory.
   • A non-root process user.
   • Dropped Linux capabilities and no-new-privileges.
   • Restricted outbound networking limited to required destinations.
   • Resource and execution-time limits.
4. Pin and regularly update Puppeteer and its compatible Chromium build so known browser vulnerabilities receive timely fixes.
5. Treat the remote page and every resource it loads as untrusted. Where feasible, restrict permitted origins and intercept requests to reject unexpected third-party destinations.

SkillSpector

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (3)

Ae1

High

• Category: analysis-evasion
• Confidence: 100% confidence

Finding

Referenced artifact was not completely inspected

Content

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

md

node scripts/generate_peep.cjs

Ae1

High

• Category: analysis-evasion
• Confidence: 100% confidence

Finding

Referenced artifact was not completely inspected

Content

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

md

node scripts/generate_peep.cjs

Ae1

High

• Category: analysis-evasion
• Confidence: 100% confidence

Finding

Referenced artifact was not completely inspected

Content

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

md

node scripts/generate_peep.cjs