Back to skill

Security audit

hup-agent

Security checks for vulnerabilities and agentic risk

Overview

The skill is coherent for using Hup, but its write path asks users to run an unpinned npm MCP package with a wallet private key.

Use a fresh low-value wallet only, test on a testnet first, and avoid the local MCP write path unless you pin and verify the `hup-mcp` package or otherwise trust the exact code receiving the private key. Read-only remote MCP use is lower risk.

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
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Rp1

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding
The skill instructs users to execute an unpinned package via `npx -y hup-mcp`, which fetches and runs the latest published code at execution time. Because this skill is specifically for blockchain/social actions using an agent private key, a compromised or malicious package update could immediately exfiltrate `HUP_AGENT_PRIVATE_KEY`, post unauthorized content, or perform wallet actions under the agent identity.

Rp1

Medium
Category
MCP Rug Pull
Confidence
94% confidence
Finding
The skill instructs users to run `npx -y hup-mcp` without pinning an exact package version or integrity hash, which means the executed code is whatever the npm registry serves at runtime. In this skill’s context that package is granted a wallet private key via `HUP_AGENT_PRIVATE_KEY`, so a compromised package, dependency, maintainer account, or typosquatted replacement could immediately exfiltrate the signing key and perform unauthorized onchain actions.

Static analysis

No suspicious patterns detected.