ClawHub
Back to skill

Security audit

angel-diligence

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed angel-investment research workflow that gathers public evidence and writes a local memo, with no hidden execution or exfiltration behavior found.

Before installing, understand that running the skill can create a local diligence memo containing company names, round details, and user-provided context. Avoid providing confidential deck details unless you are comfortable keeping them in the session and local memo; the skill explicitly says not to send deck contents to searches or external tools.

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
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Session Persistence

Medium
Category
Rogue Agent
Confidence
60% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

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

md
These rules override speed. A short memo with real citations beats a long memo with invented facts.

1. **Every factual claim needs a fetched source.** A claim goes in the memo only if you fetched a page that supports it. Cite the URL inline next to the claim. Model memory is not a source; it is stale by definition for startups.
2. **"Could not verify" is a valid finding.** If a search comes up empty, write "could not verify" next to the claim. Do not fill gaps with plausible guesses. An absence of evidence is itself a signal worth reporting.
3. **Date everything.** Every cited fact gets the date of the source page (or "undated"). Funding databases, team pages, and pricing pages go stale fast. A 14-month-old headcount number presented as current is a hallucination with a citation. Funding data is the worst offender: aggregator databases (Crunchbase mirrors, Tracxn) often miss the latest round or conflate rounds. Prefer the primary announcement, and treat any funding fact older than 6 months as possibly superseded by an unannounced round.
4. **Separate verified from claimed.** Anything sourced only from the company itself (deck, website, founder posts) is "claimed." Anything confirmed by an independent source (customer post, public repo, conference talk by a user) is "verified." Press is verified only when it quotes a customer or third party speaking from their own experience; an article that only quotes the founders or investors is still "claimed." Label each traction item as one or the other.
5. **No invented numbers.** Never state a TAM, ARR, valuation, or growth rate that does not appear in a fetched source. Market sizing must be built bottom-up from cited inputs (number of potential buyers x plausible contract value), with the arithmetic shown.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill explicitly instructs the agent to write the generated memo to a local file, but the top-level description does not clearly warn users that invoking the skill will create a filesystem artifact. In a diligence workflow, that artifact may contain sensitive company names, deck-derived notes, round details, or conflict-related context, creating an avoidable privacy and data-retention risk if the user did not expect local persistence.

Content

No source excerpt is available for this finding.