Back to skill

Security audit

Uniswap Monitor Tokenjar

Security checks for vulnerabilities and agentic risk

Overview

The skill's runtime behavior is read-only Uniswap monitoring, but its README uses unpinned, changeable install sources that could install different code than the reviewed artifact.

Install only from a pinned reviewed version or commit, avoid running the documented @latest or main-branch commands with elevated privileges, and verify the Uniswap MCP permissions before use. At runtime, the inspected skill is intended for public on-chain monitoring and analysis rather than wallet actions or transaction execution.

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

Warning
Location
README.md:9
Finding

Unpinned Third-Party Installation Sources

Content
View full analysis
Remediation
View remediation
npx clawhub@X.Y.Z install monitor-tokenjar ``` 2. Replace the mutable GitHub `main` reference with an immutable, audited commit SHA or signed release tag. 3. Where supported, verify package integrity hashes, provenance attestations, and release signatures before execution. 4. Prefer a two-stage installation process that downloads and inspects the package before executing it, rather than allowing `npx` to retrieve and immediately run changing code. 5. Publish the expected package version, repository commit, and checksums in the documentation so users can verify that they are installing the audited artifact. 6. Run installation with the minimum required privileges and avoid administrative or root accounts. ]]>
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

Rp1

Medium
Category
MCP Rug Pull
Confidence
90% confidence
Finding

The README instructs users to run npx skills add without pinning a specific package version, which means the command may fetch whatever version is current at execution time. If the upstream package is compromised, updated maliciously, or a dependency is hijacked, users could execute unreviewed code during installation.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
96% confidence
Finding

The command npx clawhub@latest install monitor-tokenjar explicitly uses the moving latest tag, which guarantees non-reproducible installs and increases supply-chain risk. An attacker who compromises the package publisher or release pipeline could deliver malicious code to anyone following the README instructions.

Content

No source excerpt is available for this finding.

External Model or Provider Selection

Medium
Category
Excessive Agency
Confidence
90% confidence
Finding

Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Content

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

md
accumulation rates, burn economics, and projected time to next profitable burn.
  Supports one-shot snapshot and streaming modes. Use when user asks "Watch the
  TokenJar", "Track fee accumulation", or "When is the next profitable burn?"
model: opus
allowed-tools:
  - Task(subagent_type:protocol-fee-seeker)
  - mcp__uniswap__get_tokenjar_balances

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The activation section says to use the skill when the user says "anything like" the listed phrases, and several examples such as "Monitor protocol fees," "Track fee accumulation," and "What's the accumulation rate?" are broad enough to overlap with other fee-monitoring contexts. Because the section does not provide negative examples beyond burn execution and deep historical analysis, the trigger scope may be interpreted too broadly.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.