other
- Location
SKILL.md:20- Finding
Uncontrolled Disclosure of Source Code to a Third-Party Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 20–27
Vulnerability Type: Sensitive Source Code Disclosure
Risk Level: MediumVulnerable Code Snippet
bash POST https://x402.ntriq.co.kr/code-review Content-Type: application/json X-PAYMENT: <x402-payment-header> { "code": "SELECT * FROM users WHERE id = '" + userId + "'", "language": "sql", "focus": "security" }Technical Analysis
The documented workflow directs the user or agent to transmit source code to the external domain
x402.ntriq.co.kr. It does not require explicit confirmation before transmission, inspect or redact embedded secrets, limit which files may be submitted, minimize the payload, or provide information about data retention and privacy controls.Repository source code may contain API keys, credentials, personal data, proprietary algorithms, internal hostnames, or infrastructure details. Following these instructions can therefore disclose sensitive information to an independently operated remote service. The request also includes an
X-PAYMENTheader, meaning each transmission may authorize a cryptocurrency payment.The external transmission is related to the advertised remote code-review functionality, so the evidence does not establish covert exfiltration or malicious intent. The security issue is the absence of controls around disclosure and payment authorization.
Attack Path
- A user or agent loads the Skill and requests a code review.
- The agent selects source code from the user's repository without a mandatory sensitivity review or explicit transmission confirmation.
- The selected content may include proprietary code, credentials, personal data, or internal infrastructure information.
- The agent sends the content in the
codefield tohttps://x402.ntriq.co.kr/code-review. - The remote service receives and may process or retain the submitted content.
- If the
X-PAYMENTheader contains a valid authorization, the re ...[truncated 741 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed user confirmation before every external transmission and clearly display:
- The destination domain.
- The exact files or content being submitted.
- The request price and payment network.
- Scan submitted content for API keys, passwords, private keys, tokens, personal data, and other secrets, and redact or block detected values.
- Exclude sensitive files by default, including environment files, credential stores, private keys, deployment configuration, and production data.
- Minimize payloads by sending only the code fragment necessary for review rather than entire files or repositories.
- Publish clear privacy, retention, deletion, encryption, and third-party processing policies for submitted source code.
- Enforce per-request confirmation, spending caps, rate limits, and cumulative budget limits for x402 payments.
- Provide a local or self-hosted review option for confidential repositories.
- Warn users not to submit proprietary or regulated data unless contractual and technical safeguards are in place.
- Require explicit, informed user confirmation before every external transmission and clearly display:
