Back to skill

Security audit

Research YC launch demos and document an OysterWorkflow demo-video plan

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed research-and-documentation workflow for OysterWorkflow demo planning, with no hidden code or malicious behavior found.

Before installing, confirm you want an agent to use your signed-in Chrome session, access ChatGPT or similar research sources, browse public YC/video pages, and create or edit a Google Doc. Verify the exact target document before allowing edits, especially if a document named “demo 计划 1” already exists.

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
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The activation guidance is broad enough to overlap with ordinary research, marketing, and planning work, which can cause the agent to invoke this skill in situations the user did not specifically intend. Because the skill performs downstream actions like browsing and editing documents, ambiguous triggering increases the chance of unintended external actions and document modifications.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill explicitly states there are no exclusions, leaving no guardrails for adjacent tasks where this workflow may be inappropriate. In practice, that ambiguity can cause over-application of a skill that opens sites and updates an existing Google Doc, creating a real risk of unintended modifications or unnecessary data exposure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill directs the agent to use and update a named Google Doc but does not require an explicit user confirmation immediately before modifying that existing document. This is dangerous because it can lead to silent overwrites, contamination of prior notes, or edits to the wrong document if multiple similarly named files exist.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
72% confidence
Finding

The guidance suggests a specific English CTA: 'Send us a workflow your team still does by hand. We’ll turn it into an AI skill.' Elsewhere the document mixes English and Chinese, but it does not state that output language should follow user preference or that English is required for a justified business reason.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.