T08 · Insecure Dependencies
- Location
SKILL.md:136- Finding
Unpinned Third-Party Package Is Downloaded and Executed Automatically
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent remote Japan business knowledge service, but it asks users to run unpinned external MCP code and use externally retained memory without enough safeguards.
Review before installing. Basic API queries are consistent with the skill's purpose, but avoid sending confidential business plans, personal data, regulated information, or secrets. Do not enable the MCP server unless you have reviewed or pinned the npm package, and treat the memory feature as external retained storage until the publisher documents retention, deletion, and access controls.
SKILL.md:136Unpinned Third-Party Package Is Downloaded and Executed Automatically
SKILL.md:48Shared Bearer Credential Is Hardcoded in Public Skill Instructions
SKILL.md:118Persistent Memory Workflow Can Transmit Personal or Confidential Context Without Safeguards
The authentication and usage examples normalize sending business queries and later memory content to a third-party API, but there is no user-facing disclosure that prompts and operational data leave the local environment. This is risky because users may assume the skill is a local knowledge base and inadvertently transmit proprietary or sensitive information.
This example sends a user query to an external API endpoint, which is a real data egress behavior. While external API usage is expected for a hosted knowledge service, the danger is that the skill presents this without strong warning that task content may be disclosed to a third party.
Search all 10 knowledge domains simultaneously with a single query.
curl -X POST https://api.edition.sh/api/v1/search \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "opening a restaurant in Osaka"}'
This example sends a user query to an external API endpoint, which is a real data egress behavior. While external API usage is expected for a hosted knowledge service, the danger is that the skill presents this without strong warning that task content may be disclosed to a third party.
Search all 10 knowledge domains simultaneously with a single query.
curl -X POST https://api.edition.sh/api/v1/search \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "opening a restaurant in Osaka"}'
The regulation-check example transmits operational business intent and entity details to an external service. In context this is expected product behavior, but it still creates confidentiality risk if users submit sensitive expansion plans, legal matters, or client data without warning.
curl -X POST https://api.edition.sh/api/v1/regulation/check \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"action": "open a restaurant in Tokyo", "entity_type": "foreign_company"}'
The protocol-check example sends a query to an external endpoint, creating ordinary network data exposure. The content shown is low sensitivity, so the primary issue is lack of transparency rather than inherently dangerous functionality.
curl -X POST https://api.edition.sh/api/v1/protocol/check \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "business card exchange"}'
The foreign-entry example submits immigration- and market-entry-related questions to an outside API, which may reveal sensitive legal or strategic information about a person or company. The skill does not pair this with any privacy or data-sharing warning.
curl -X POST https://api.edition.sh/api/v1/foreign-entry/check \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "how to get a management visa"}'
This calendar-intelligence example causes outbound transmission of user queries to a remote service. The example itself is low sensitivity, but the skill still lacks disclosure that user inputs leave the local environment.
curl -X POST https://api.edition.sh/api/v1/calendar/check \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "best time to start a business in Japan"}'
The travel-search example transmits user queries to a third-party API. The risk is limited by the benign sample content, but it remains a real egress path that should be disclosed to users.
curl -X POST https://api.edition.sh/api/v1/travel/search \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "ryokan etiquette"}'
The persistent memory examples explicitly store personal and business context such as meeting notes and individual preferences in an external service, but the skill does not warn about retention, access scope, or privacy consequences. In an agent setting, users may upload sensitive personal data, confidential business details, or regulated information without informed consent or data minimization.
This memory-store example sends personally attributable meeting notes and preference data to an external API, making the data exposure concrete rather than hypothetical. In a business-agent context, such memory entries can easily contain confidential relationship details, personal data, and internal intelligence, amplifying privacy and compliance risk.
# Store
curl -X POST https://api.edition.sh/api/v1/memory/episodes \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"content": "Met with Tanaka-bucho. He prefers informal meetings.", "auto_extract": true}'
The memory-search example queries externally stored memory, confirming that prior sensitive content may be indexed and retrievable by a remote service. This increases the risk of unintended disclosure and creates an expectation of persistent off-platform storage without adequate warning.
-d '{"content": "Met with Tanaka-bucho. He prefers informal meetings.", "auto_extract": true}'
# Recall
curl -X POST https://api.edition.sh/api/v1/memory/episodes/search \
-H "Authorization: Bearer edition_dev_key_for_testing" \
-H "Content-Type: application/json" \
-d '{"query": "what does Tanaka prefer"}'
The skill instructs users to run an MCP server via npx -y edition-mcp-server without pinning a specific version or integrity hash. That causes execution of whatever package is current at install time, creating a supply-chain risk if the package is compromised, replaced, or updated with unsafe behavior.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Links
- **API Docs**: https://api.edition.sh/docs
- **Landing Page**: https://edition.sh
- **GitHub**: https://github.com/hiroshic9-png/edition-api
- **npm**: https://www.npmjs.com/package/edition-mcp-server
Detected: suspicious.exposed_secret_literal