Back to skill

Security audit

psilo

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent escrow documentation, but it contains unsafe financial transaction guidance that could cause token loss if followed.

Review this skill carefully before installing or using it with real funds. Do not follow the ERC-20 deposit snippet as written unless the escrow contract documentation independently confirms direct token transfer is correct; prefer SDK-provided approve/deposit payloads, pin and audit wallet/signing dependencies, decode every transaction before signing, and test on testnets with small limits first.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T08 · Insecure Dependencies

Warning
Location
skill.md:112
Finding

Unpinned Third-Party Dependencies Handle Wallet Keys and Financial Transactions

Content
View full analysis
Remediation
View remediation
npm install --save-exact @pakt/psilo@ npm install --save-exact @buildersgarden/siwa@ ``` 2. Provide and enforce a reviewed lockfile using `npm ci` rather than unconstrained `npm install`. 3. Verify package provenance, publisher identity, signatures or attestations, and registry integrity metadata. 4. Audit direct and transitive dependencies before upgrades. Treat wallet and signing package updates as security-sensitive changes requiring renewed review. 5. Disable installation scripts where operationally possible, for example with `npm ci --ignore-scripts`, after confirming required package behavior. 6. Run wallet and transaction preparation components with minimal filesystem and environment access. 7. Keep signing isolated from network-facing SDK code. Before signing, independently decode and verify the chain ID, target contract, function selector, recipient, token, amount, nonce, and value. 8. Require explicit user approval for the final decoded transaction rather than trusting the SDK's prepared payload. 9. Protect wallet files with strict filesystem permissions and avoid exposing unrelated secrets to the signing process. ]]>

T09 · Insecure Skill Coding Practices

Error
Location
skill.md:365
Finding

ERC-20 Deposit Example Transfers Tokens Instead of Approving the Escrow

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The ERC20 deposit example is internally inconsistent: it says to approve the escrow contract to spend tokens, but the code actually encodes and sends a direct transfer to the escrow address. In an escrow workflow, this can strand tokens if the contract expects approve followed by deposit(), causing funds to be moved in a way the escrow logic may not recognize and potentially making assets unrecoverable.

Content

No source excerpt is available for this finding.

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 5)May include surrounding context.

md
name: psilo
version: 1.0.1
description: >
  Use this skill when an agent needs to: (1) create on-chain escrow contracts via EscrowFactory,
  (2) release escrowed funds via arbiter-signed transactions, and (3) interact with the Pakt Escrow
  service using the @pakt/psilo SDK. Authentication and wallet: choose SIWA or Evalanche.
---

Skill Enumeration

Medium
Category
Agent Snooping
Confidence
80% confidence
Finding

Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Content

Scanner excerpt · skill.md (reported line 108)May include surrounding context.

md
- **If the agent does not yet have a wallet:** Follow the [SIWA skill documentation](https://siwa.id/skill.md) to:
     - Install and configure SIWA using the `@buildersgarden/siwa` package
     - Choose and set up an agent-side wallet (e.g. [Private Key](https://siwa.id/skills/private-key/skill.md), [Keyring Proxy](https://siwa.id/skills/keyring-proxy/skill.md), or another [wallet skill](https://siwa.id/skill.md#skills) listed there)
     - **Register the agent on the ERC-8004 Identity Registry** (see [siwa.id/skill.md](https://siwa.id/skill.md) and the `@buildersgarden/siwa/registry` module)
     - Authenticate via SIWA to obtain a receipt for agent endpoints
   - **If the agent already has a wallet:** Ensure it is registered on ERC-8004 and that you can authenticate via SIWA to get a receipt when calling agent-only endpoints.

Skill Enumeration

Medium
Category
Agent Snooping
Confidence
80% confidence
Finding

Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Content

Scanner excerpt · skill.md (reported line 108)May include surrounding context.

md
- **If the agent does not yet have a wallet:** Follow the [SIWA skill documentation](https://siwa.id/skill.md) to:
     - Install and configure SIWA using the `@buildersgarden/siwa` package
     - Choose and set up an agent-side wallet (e.g. [Private Key](https://siwa.id/skills/private-key/skill.md), [Keyring Proxy](https://siwa.id/skills/keyring-proxy/skill.md), or another [wallet skill](https://siwa.id/skill.md#skills) listed there)
     - **Register the agent on the ERC-8004 Identity Registry** (see [siwa.id/skill.md](https://siwa.id/skill.md) and the `@buildersgarden/siwa/registry` module)
     - Authenticate via SIWA to obtain a receipt for agent endpoints
   - **If the agent already has a wallet:** Ensure it is registered on ERC-8004 and that you can authenticate via SIWA to get a receipt when calling agent-only endpoints.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The release-readiness section shows updateStatus calls for seller/buyer readiness but then presents a response structure containing release-result fields like txHash, arbiter, and release success. This can mislead integrators into implementing the wrong control flow around a high-risk financial operation, increasing the chance of incorrect transaction handling, skipped checks, or unsafe assumptions about when funds are actually releasable.

Content

No source excerpt is available for this finding.