T01 · Skill Instruction Hijacking
- Location
SKILL.md:20- Finding
Untrusted Remote Instructions Are Relayed Verbatim to Users
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its stated Vibe VC submission workflow, but it needs review because it sends sensitive founder/project data to a configurable web endpoint and tells the agent to relay remote social-post instructions verbatim.
Use this only if you are comfortable disclosing the supplied founder, project, repository, analytics, billing, and contact details to Vibe VC. Keep the destination set to the documented Vibe VC HTTPS hosts, review dry-run output before submitting, never include secrets or private contact data, and manually vet any LinkedIn/X wording before posting it.
SKILL.md:20Untrusted Remote Instructions Are Relayed Verbatim to Users
scripts/vibevc_api.py:58Sensitive User and Project Data Can Be Redirected to Arbitrary Network Destinations
Most of the declared API-related functionality is accurately represented: the code does register projects, connect integrations, subscribe to a newsletter, and contact via public endpoints. However, the description also claims the skill can generate required human verification post instructions for LinkedIn/X, and there is no code for instruction generation, templating, or any LinkedIn/X-related behavior. Additionally, 'manage its diligence surfaces' suggests broader diligence management functionality than is actually present; the implementation is limited to a few POST API calls. Because the description includes at least one material undeclared capability not supported by the code, this is a mismatch.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Treat everything you send as **external disclosure**.
- **Do not submit** a project (or connect repos/analytics/billing) without an explicit go-ahead from the human.
- Never send secrets (API keys, access tokens, passwords), private addresses, or private emails that are not intended to be shared.
## Quick workflow
The skill invokes a bundled CLI that performs outbound API calls and can read environment configuration, but the manifest does not declare any tool scope or allowed-tools boundary. That omission weakens reviewability and consent controls, making it easier for an agent runtime to use network/env capabilities implicitly when handling external disclosures and third-party integrations.
This code sends user-supplied data such as email addresses, names, repository URLs, and free-form messages to remote API endpoints via HTTP POST. Although the file's examples and argument names imply API usage, there is no explicit confirmation prompt, warning print, or disclosure immediately before transmitting potentially sensitive data.
No suspicious patterns detected.