T09 · Insecure Skill Coding Practices
Warning
- Location
references/auth-setup.md:5- Finding
Persistent Plaintext Storage and Command-Line Exposure of API Credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Vrbo availability
Security checks for vulnerabilities and agentic risk
Overview
The skill’s API use fits its purpose, but its setup instructions push users to persist a live API key across future sessions without clear secret-storage safeguards.
Install only if you are comfortable using StayingAPI for Vrbo availability checks. Prefer a sandbox key for evaluation, avoid placing live keys in general shell profiles, and store any live key in a protected secret manager or narrowly scoped runtime secret configuration that you can revoke or rotate.
Vulnerability Patterns
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)
Vulnerability Patterns
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
- Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
Step 3 — verify
bash curl -s "https://api.stayingapi.com/v1/account" -H "Authorization: Bearer $STAYINGAPI_KEY" | headA
200with your account envelope means the key works. A missing/invalid key returns401 authentication_error(never billed). Full contract: https://api.stayingapi.com/openapi.json.
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
Step 3 — verify
bash curl -s "https://api.stayingapi.com/v1/account" -H "Authorization: Bearer $STAYINGAPI_KEY" | headA
200with your account envelope means the key works. A missing/invalid key returns401 authentication_error(never billed). Full contract: https://api.stayingapi.com/openapi.json.
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
Step 3 — verify
bash curl -s "https://api.stayingapi.com/v1/account" -H "Authorization: Bearer $STAYINGAPI_KEY" | headA
200with your account envelope means the key works. A missing/invalid key returns401 authentication_error(never billed). Full contract: https://api.stayingapi.com/openapi.json.
External Transmission
Medium
- Category
- Data Exfiltration
- Confidence
- 50% confidence
- Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
- Content
Step 3 — verify
bash curl -s "https://api.stayingapi.com/v1/account" -H "Authorization: Bearer $STAYINGAPI_KEY" | headA
200with your account envelope means the key works. A missing/invalid key returns401 authentication_error(never billed). Full contract: https://api.stayingapi.com/openapi.json.
Static analysis
No suspicious patterns detected.