Back to skill

Security audit

go-surge

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward guide for using an unofficial Go client for the Surge SMS API, with sensitive actions disclosed and aligned to its purpose.

Install this only for Go projects that intentionally need Surge SMS API access. Treat SURGE_API_KEY as a sensitive credential, review any code that sends messages or changes accounts, users, phone numbers, recordings, or tokens, and confirm destructive or billing-affecting actions before running them.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (6)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 34)May include surrounding context.

md
| Methods, each with a WithResponse suffix | Endpoint |
|---|---|
| `ListAccounts`, `CreateAccount` | `GET`, `POST /accounts` |
| `GetAccount`, `UpdateAccount`, `ArchiveAccount` | `GET`, `PATCH`, `DELETE /accounts/{id}` |
| `CheckAccountStatus` | `GET /accounts/{account_id}/status` |
| `CreateAudience` | `POST /accounts/{account_id}/audiences` |
| `ListAudienceContacts`, `AddContactToAudience` | `GET`, `POST /audiences/{audience_id}/contacts` |

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 49)May include surrounding context.

md
| `GetAttachmentFile` | `GET /attachments/{attachment_id}/file` |
| `ListAvailablePhoneNumbers` | `GET /accounts/{account_id}/available_phone_numbers` |
| `ListPhoneNumbers`, `PurchasePhoneNumber` | `GET`, `POST /accounts/{account_id}/phone_numbers` |
| `GetPhoneNumber`, `UpdatePhoneNumber`, `ReleasePhoneNumber` | `GET`, `PATCH`, `DELETE /phone_numbers/{id}` |
| `ListRecordings` | `GET /accounts/{account_id}/recordings` |
| `GetRecording`, `DeleteRecording` | `GET`, `DELETE /recordings/{id}` |
| `GetRecordingFile` | `GET /recordings/{recording_id}/file` |

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 51)May include surrounding context.

md
| `ListPhoneNumbers`, `PurchasePhoneNumber` | `GET`, `POST /accounts/{account_id}/phone_numbers` |
| `GetPhoneNumber`, `UpdatePhoneNumber`, `ReleasePhoneNumber` | `GET`, `PATCH`, `DELETE /phone_numbers/{id}` |
| `ListRecordings` | `GET /accounts/{account_id}/recordings` |
| `GetRecording`, `DeleteRecording` | `GET`, `DELETE /recordings/{id}` |
| `GetRecordingFile` | `GET /recordings/{recording_id}/file` |
| `ListUsers`, `CreateUser` | `GET`, `POST /accounts/{account_id}/users` |
| `GetUser`, `UpdateUser`, `DeleteUser` | `GET`, `PATCH`, `DELETE /users/{id}` |

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 54)May include surrounding context.

md
| `GetRecording`, `DeleteRecording` | `GET`, `DELETE /recordings/{id}` |
| `GetRecordingFile` | `GET /recordings/{recording_id}/file` |
| `ListUsers`, `CreateUser` | `GET`, `POST /accounts/{account_id}/users` |
| `GetUser`, `UpdateUser`, `DeleteUser` | `GET`, `PATCH`, `DELETE /users/{id}` |
| `CreateToken` | `POST /users/{user_id}/tokens` |
| `CreateVerification` | `POST /accounts/{account_id}/verifications` |
| `CheckVerification` | `POST /verifications/{id}/checks` |

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The operations table includes destructive endpoints such as ArchiveAccount, ReleasePhoneNumber, DeleteRecording, and DeleteUser, but the documentation does not warn that these actions may remove data or change account state irreversibly. For markdown files, omission of warnings about behaviors affecting user data or system integrity is in scope.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

This markdown file instructs users to export SURGE_API_KEY and attach it as a bearer token in HTTP requests, but it provides no warning about keeping the token secret, avoiding logging it, or using a secure storage mechanism. Because the file documents credential use and transmission, a brief user-facing warning would improve safety and meet the missing-warning criterion for markdown files.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.