Back to skill

Security audit

Decanus Escrow

Security checks for vulnerabilities and agentic risk

Overview

The skill matches its escrow purpose, but it asks users to run unpinned npm code with a wallet private key capable of signing onchain transactions.

Review carefully before installing. Use only a dedicated low-value testnet key, avoid production or reused wallet keys, pin the npm package version if possible, and require explicit human review before any state-changing escrow transaction.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Error
Location
SKILL.md:31
Finding

Unpinned npm Package Executes with Access to a Wallet Private Key

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (3)

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding

The skill instructs users to execute an unpinned package directly with npx, which will fetch the latest published version at runtime. In a security-sensitive escrow skill that requires a blockchain private key, a compromised maintainer account, malicious update, or dependency hijack could immediately lead to key theft or unauthorized onchain transactions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The documentation shows PRIVATE_KEY=0x... inline and in config without any explicit warning about secret-handling, key scoping, or exposure risks. In a crypto payment skill, this is especially dangerous because users may paste real wallet keys into shell history, config files, logs, or shared agent settings, enabling theft of funds and impersonation of the signer.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
88% confidence
Finding

The MCP configuration also launches the server via unpinned npx, creating the same supply-chain risk but in a more persistent agent/plugin context. Because this skill is designed to hold a PRIVATE_KEY in environment variables, an unexpected upstream package update could exfiltrate credentials or submit transactions without user intent.

Content

No source excerpt is available for this finding.