T09 · Insecure Skill Coding Practices
- Location
SKILL.md:321- Finding
Ed25519 Private Signing Key Disclosed Through Standard Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This guide is not self-executing, but it requests high-value payment and signing secrets and includes unsafe examples that could expose keys or run real payment operations.
Review before installing. Use only sandbox/test credentials, avoid providing Stripe or signing keys unless a specific workflow actually needs them, do not paste production secrets into shell examples, and do not run the private-key example as written because it prints secret key material.
SKILL.md:321Ed25519 Private Signing Key Disclosed Through Standard Output
SKILL.md:14Unused Signing and Payment Credentials Requested Beyond Functional Need
The guide presents inconsistent security-relevant setup information: it claims the sandbox requires no API key while also declaring required credentials and showing authenticated examples. This can mislead users into supplying real credentials unnecessarily or misunderstanding which environment they are targeting, increasing the chance of accidental credential exposure or misuse.
The guide includes authenticated curl and Python examples for payment-related operations without strong warnings to use sandbox/test credentials only or to avoid exposing secrets in shell history, logs, notebooks, and console output. Users may paste real API keys and payment tokens into terminals or shared environments, leading to credential leakage and unauthorized API usage.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
You need two things:
requests and cryptography installedData is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
You need two things:
requests and cryptography installedData is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
You need two things:
requests and cryptography installedData is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
def execute_tool(tool: str, input_data: dict) -> dict:
"""Execute a tool on the GreenHelix A2A Commerce Gateway."""
response = requests.post(
f"{BASE_URL}/v1",
headers={
"Content-Type": "application/json",
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
export GREENHELIX_API_KEY="your-api-key-here"
curl -s -X POST https://sandbox.greenhelix.net/v1 \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $GREENHELIX_API_KEY" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"""Execute a tool with retry logic for transient errors."""
for attempt in range(retries + 1):
try:
resp = requests.post(
f"{BASE_URL}/v1",
headers={"Content-Type": "application/json",
"Authorization": f"Bearer {API_KEY}"},
The example generates a private signing key and prints it directly to stdout, which is highly risky because terminals, notebooks, CI logs, shell history capture, and observability tools may retain secret material. Exposure of the signing key would allow impersonation of the agent and fraudulent signing of payment or identity-related actions.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
```bash
# curl equivalent
curl -s -X POST https://sandbox.greenhelix.net/v1 \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $GREENHELIX_API_KEY" \
The opening notice frames the file as purely illustrative and non-executing, yet the guide later includes concrete code that issues authenticated HTTP POST requests to GreenHelix endpoints and demonstrates creating payment intents, escrows, and disputes. While the markdown itself does not execute, the wording can be read as minimizing the real side effects of the provided code snippets.