T09 · Insecure Skill Coding Practices
- Location
EXAMPLES.md:354- Finding
Inbox API Key Exposed in a Dashboard URL Query String
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent bot-email integration, but it needs review because it handles verification codes and API keys while documenting destructive inbox actions and an unsafe dashboard URL pattern.
Install only if you are comfortable sending bot inbox contents, verification emails, and codes to BotEmail.ai. Treat the returned API key like a password, avoid sharing dashboard URLs that contain keys, do not use this for high-value or regulated accounts, and require explicit confirmation before deleting messages or clearing an inbox. Use the optional MCP server only from a pinned, reviewed commit in an isolated environment.
EXAMPLES.md:354Inbox API Key Exposed in a Dashboard URL Query String
README.md:164Optional MCP Installation Uses an Unpinned Remote Repository and Dependency Graph
The documented delete-by-ID endpoint exposes a destructive capability over a user-controlled parameter without any stated confirmation, authorization scoping, or safety constraints beyond possession of the API key. In an agent workflow, this creates a realistic risk that prompt confusion, bad tool routing, or malicious instruction could cause deletion of messages that may contain important verification or audit information.
### GET /api/emails/{email}/{id}
Get a single email by ID.
### DELETE /api/emails/{email}/{id}
Delete a specific email.
### DELETE /api/emails/{email}
The clear-entire-inbox endpoint is especially dangerous because a single request can irreversibly remove all stored messages, including verification codes, testing evidence, and notifications. In this skill context, where inboxes are used for automated workflows and authentication-related emails, accidental or manipulated invocation could disrupt accounts and destroy useful records at scale.
### DELETE /api/emails/{email}/{id}
Delete a specific email.
### DELETE /api/emails/{email}
Clear entire inbox.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
```bash
# Create random bot email (no username needed)
curl -X POST https://api.botemail.ai/api/create-account \
-H "Content-Type: application/json" \
-d '{}'
```
The examples display an API key and later demonstrate extracting verification codes, but the surrounding documentation does not prominently warn that these values grant mailbox access and can expose account verification flows. In agent or demo contexts, readers may copy logging patterns or share outputs, leading to credential leakage and unauthorized inbox access.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function autoVerifyEmail(serviceName) {
// 1. Create bot email
const accountResponse = await fetch('https://api.botemail.ai/api/create-account', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({})
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function autoVerifyEmail(serviceName) {
// 1. Create bot email
const accountResponse = await fetch('https://api.botemail.ai/api/create-account', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({})
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
async function autoVerifyEmail(serviceName) {
// 1. Create bot email
const accountResponse = await fetch('https://api.botemail.ai/api/create-account', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({})
The cleanup example performs permanent deletion of emails but does not clearly warn that the action is destructive and irreversible. Users may run it as-is against active inboxes and unintentionally destroy messages, including evidence, verification emails, or operational data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
});
// 2. Register webhook with BotEmail.ai
await fetch('https://api.botemail.ai/api/webhook/register', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
No suspicious patterns detected.