Back to skill

Security audit

SMS Best Practices

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly ordinary SMS guidance, but one troubleshooting instruction could tell an agent to bypass marketing quiet-hour protections by relabeling a message as transactional.

Review the quiet-hours guidance before installing. The skill should be changed so marketing messages blocked during quiet hours are delayed or scheduled for a permitted recipient-local time, never relabeled as transactional unless the content and consent basis are genuinely transactional.

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
Findings (1)

other

Warning
Location
SKILL.md:91
Finding

SMS Quiet-Hours Compliance Bypass Through Message-Type Misclassification

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 91
Vulnerability Type: Compliance-control bypass guidance
Risk Level: Medium

Vulnerable Code Snippet

markdown
| `quiet_hours_violation` | Marketing during 9pm–8am | Use transactional type or wait |

Technical Analysis

The remediation text suggests using the transactional message type when a marketing message is blocked by quiet-hours enforcement. This permits an operator or AI agent to change the classification without changing the message's actual purpose.

Message type is a compliance property determined by content, recipient relationship, and consent—not a mechanism for bypassing delivery restrictions. The guidance also conflicts with SKILL.md lines 22–29, which distinguish transactional traffic from marketing traffic and explicitly warn that misclassification may violate the TCPA.

An agent following the error table could interpret reclassification as an approved workaround and submit marketing content as transactional. Because the document states that transactional messages are exempt from quiet hours, this would bypass the intended compliance control.

Attack Path

  1. An operator or automated agent attempts to send a marketing SMS during the recipient's quiet hours.
  2. Sendly rejects the request with quiet_hours_violation.
  3. The agent consults the error-remediation table in SKILL.md.
  4. Following the instruction “Use transactional type or wait,” the agent changes the message type from marketing to transactional without changing its promotional purpose.
  5. The quiet-hours restriction no longer applies according to the documented behavior.
  6. The marketing message is delivered during otherwise prohibited hours.

Impact Assessment

This issue does not grant operating-system privileges, access to credentials, or code-execution capabilities. Its scope is limited to SMS classification and delivery behavior.

However, i ...[truncated 404 chars]

Remediation
View remediation

Remediation Suggestions

Replace the affected remediation with unambiguous guidance such as:

markdown
| `quiet_hours_violation` | Marketing during 9pm–8am | Wait until permitted recipient-local hours. Never relabel marketing content as transactional to bypass quiet hours. |

Apply the following hardening measures:

  1. State explicitly that message classification must reflect the message's actual purpose, content, consent basis, and recipient relationship.
  2. Prohibit changing a marketing message to transactional solely to avoid quiet-hours restrictions.
  3. Require delayed scheduling based on the recipient's local timezone when a legitimate marketing send is blocked.
  4. Add examples showing the difference between genuinely transactional content and promotional content.
  5. If implemented in software, validate message content and campaign metadata against the selected type and reject inconsistent classifications.
  6. Record classification decisions and consent evidence in audit logs for compliance review.
  7. Add tests confirming that marketing content remains subject to quiet hours even when a caller attempts to label it as transactional.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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