T01 · Skill Instruction Hijacking
- Location
SKILL.md:64- Finding
Mutable Remote Skill Instructions Can Bypass Package Review
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is openly about an autonomous USDC job marketplace, but it gives agents live wallet-signing and payment authority with weak scoping and mutable update paths.
Review before installing. Use only a dedicated low-balance wallet, pin SDK and runner versions, avoid loading the remote always-latest skill as trusted instructions, keep MDP_AUTO_PROPOSE disabled unless policy checks are in place, and do not run buyer mode until payment requirements, destinations, and spend limits are independently verified.
SKILL.md:64Mutable Remote Skill Instructions Can Bypass Package Review
pager.md:497Unpinned Packages Execute with Access to the Wallet Environment
pager.md:74Configurable API Origin Can Solicit Wallet Authentication Signatures
pager.md:404Autonomous Buyer Blindly Signs Server-Supplied Payment Requirements
A skill described as a pager requires an on-chain private key and later demonstrates authenticated payment signing and settlement. Combining message/job polling with wallet-key based authority substantially raises risk: compromise, misuse, or misconfiguration of the running agent can lead to unauthorized proposals, message actions, and potentially irreversible financial transactions.
The buyer-mode quick-start walks directly from job creation to sdk.payments.fundJob(...) without a clear caution that this can initiate a live blockchain payment using the configured private key. In a skill for autonomous agents, concise code snippets are often copied verbatim, so omitting a real-funds warning materially raises the risk of unintended escrow deposits.
The skill explicitly promotes autonomous escrow funding and presents fundJob() as a normal workflow step, but it does not place a prominent warning near that guidance that this signs real EIP-3009 authorizations and may trigger irreversible on-chain USDC transfers. For an agent skill intended for autonomous execution, that omission increases the chance that users enable live payment flows without understanding they are authorizing real fund movement.
The autonomous pager protocol includes MDP_AUTO_PROPOSE and pseudocode for unattended proposal submission, but it does not prominently warn that enabling this allows an agent to take marketplace actions on its own behalf without human review. While proposal submission is less severe than direct fund transfer, it can still create contractual, reputational, and operational risk through spam, accidental commitments, or engagement with malicious job postings.
The skill instructs agents to poll unread direct messages, fetch their contents, process them, and mark conversations as read, but it does not prominently warn users that private communications will be continuously accessed and state will be modified. In an autonomous agent context, silent message access can create privacy, consent, and auditability issues, especially if operators assume the pager is only checking job listings.
The skill describes autonomous proposal submission, proposal acceptance, and escrow/payment settlement without a prominent up-front warning that these actions can commit funds or alter marketplace workflow irreversibly. In this context, automation tied to a private key and payment signer makes omissions around operator consent more dangerous, because a user may deploy it as a benign monitor and inadvertently authorize spending or contractual commitments.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The file is presented as a pager/heartbeat protocol, but it also includes buyer-mode logic that accepts proposals, initiates escrow payments, signs payment material, and settles on-chain transactions. That scope expansion is dangerous because operators may enable or reuse the code expecting passive monitoring, while it actually performs financially consequential state-changing actions.
No suspicious patterns detected.