other
- 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: MediumVulnerable Code Snippet
markdown | `quiet_hours_violation` | Marketing during 9pm–8am | Use transactional type or wait |Technical Analysis
The remediation text suggests using the
transactionalmessage 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.mdlines 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
- An operator or automated agent attempts to send a marketing SMS during the recipient's quiet hours.
- Sendly rejects the request with
quiet_hours_violation. - The agent consults the error-remediation table in
SKILL.md. - Following the instruction “Use transactional type or wait,” the agent changes the message type from marketing to transactional without changing its promotional purpose.
- The quiet-hours restriction no longer applies according to the documented behavior.
- 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:
- State explicitly that message classification must reflect the message's actual purpose, content, consent basis, and recipient relationship.
- Prohibit changing a marketing message to transactional solely to avoid quiet-hours restrictions.
- Require delayed scheduling based on the recipient's local timezone when a legitimate marketing send is blocked.
- Add examples showing the difference between genuinely transactional content and promotional content.
- If implemented in software, validate message content and campaign metadata against the selected type and reject inconsistent classifications.
- Record classification decisions and consent evidence in audit logs for compliance review.
- Add tests confirming that marketing content remains subject to quiet hours even when a caller attempts to label it as transactional.
