Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md For the raw OpenAPI 3.0 spec, see [references/openapi.json](references/openapi.json).
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not malware, but it can send real email and modify or delete Pakat mailing-list data without strong built-in confirmation guidance.
Install only if you intend to let the agent operate a live Pakat email-marketing account. Use the least-privileged API key available, require a preview and explicit confirmation for sends, deletes, imports, unsubscribes, and list changes, and handle subscriber/tracking data according to your privacy and consent obligations.
Referenced artifact was not completely inspected
For the raw OpenAPI 3.0 spec, see [references/openapi.json](references/openapi.json).
The trigger description is broad enough to activate on generic email-related requests, which can route users into a high-impact skill that manages real mailing lists, subscribers, and outbound campaigns. In this context, unintended invocation is dangerous because the skill can perform external state-changing actions against a live third-party service using stored credentials.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# GET requests
curl -s -H "X-API-KEY: $PAKAT_API_KEY" "https://new.pakat.net/api/{endpoint}"
# POST requests (multipart/form-data)
curl -s -X POST -H "X-API-KEY: $PAKAT_API_KEY" \
The skill documents creating and sending campaigns and transactional emails but does not require an explicit warning or confirmation before executing actions that contact real recipients. This increases the risk of accidental bulk email, unwanted transactional messages, compliance issues, and reputational damage if the agent proceeds from ambiguous user intent.
This markdown file lists destructive endpoints such as deleting lists, subscribers, fields, segments, campaigns, templates, and transactional emails, but provides no warning that these actions may be irreversible or affect user data. Under the markdown-specific warning criterion, documentation should disclose behaviors that can impact data integrity.
The file documents endpoints for tracking opens, clicks, unsubscribes, and searching subscribers by email across lists, which involve personal data and behavioral tracking. There is no accompanying warning about privacy implications, consent requirements, or careful handling of subscriber data.
The spec includes additional administrative capabilities such as sending-domain lookup and quota inspection that are omitted from the manifest description. While lower risk than write operations, hidden administrative endpoints increase the chance of unreviewed data exposure and make the skill's real authority broader than users expect.
The skill exposes multiple destructive delete operations for campaigns, lists, templates, subscribers, and transactional emails without any warning or confirmation semantics in the manifest. In an agentic context, this makes accidental or prompt-induced irreversible deletion more likely, especially because the API key appears to permit direct state-changing actions.
The spec includes additional administrative capabilities such as sending-domain lookup and quota inspection that are omitted from the manifest description. While lower risk than write operations, hidden administrative endpoints increase the chance of unreviewed data exposure and make the skill's real authority broader than users expect.
No suspicious patterns detected.