T08 · Insecure Dependencies
- Location
SKILL.md:107- Finding
Unpinned Third-Party Package Execution with a Sensitive Wallet Credential
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent podcast research API skill, but its optional paid wallet workflow documents unpinned local package execution with a sensitive wallet credential.
Use the free tier or a normal wallet first. If using paid access, treat L402 and NWC values as bearer credentials, use a low-balance wallet with strict limits, avoid the unpinned `npx` command unless you have independently verified and pinned the package, and do not upload sensitive/private research material into sessions or public share links.
SKILL.md:107Unpinned Third-Party Package Execution with a Sensitive Wallet Credential
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.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
description: "Jamie API — podcast search, research sessions, corpus browsing, RSS feed ingestion, clip generation (all endpoints proxied for security)"
externalTools:
- name: "Lightning wallet (any)"
description: "For paid tier only: Any Lightning wallet (Zeus, BlueWallet, Phoenix, Alby extension, etc.) to pay BOLT-11 invoices. NO CLI tools are required or auto-executed by this skill."
required: false
---
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
description: "Jamie API — podcast search, research sessions, corpus browsing, RSS feed ingestion, clip generation (all endpoints proxied for security)"
externalTools:
- name: "Lightning wallet (any)"
description: "For paid tier only: Any Lightning wallet (Zeus, BlueWallet, Phoenix, Alby extension, etc.) to pay BOLT-11 invoices. NO CLI tools are required or auto-executed by this skill."
required: false
---
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
description: "Jamie API — podcast search, research sessions, corpus browsing, RSS feed ingestion, clip generation (all endpoints proxied for security)"
externalTools:
- name: "Lightning wallet (any)"
description: "For paid tier only: Any Lightning wallet (Zeus, BlueWallet, Phoenix, Alby extension, etc.) to pay BOLT-11 invoices. NO CLI tools are required or auto-executed by this skill."
required: false
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -D- -X POST -H "Content-Type: application/json" \
-d '{"query": "bitcoin energy consumption"}' \
"https://www.pullthatupjamie.ai/api/search-quotes"
The skill documentation recommends running npx @getalby/cli without pinning a specific version. This creates a supply-chain risk because a future compromised or malicious package version could be fetched and executed at runtime on the operator's machine. The risk is somewhat reduced because the command is presented as optional manual usage rather than auto-executed by the skill.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://www.pullthatupjamie.ai/api/make-clip \
-H "Content-Type: application/json" \
-d '{"clipId": "1015378_guid_p123"}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST \
-H "Authorization: L402 MACAROON:PREIMAGE" \
-H "Content-Type: application/json" \
-d '{"query": "that time Jim talked about the AI monolith", "smartMode": true, "limit": 10}' \
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Step 1: Find the feed
curl -s "API_BASE/api/corpus/feeds?search=News+and+Guidance"
# Returns: feedId (e.g., 7648986)
# Step 2: Search episode titles within that feed
The session-creation workflow instructs clients to upload full clip metadata, including transcript text, audio URLs, listen links, dates, images, and a client identifier derived from a payment hash, to an external service. In context this is expected product behavior, but it still creates a real data-transfer risk because user-curated research content and identifiers are sent off-platform and could expose sensitive or proprietary material if agents include private data or misuse credentials.
curl -s -X POST \
-H "Authorization: L402 MACAROON:PREIMAGE" \
-H "Content-Type: application/json" \
-d '{
No suspicious patterns detected.