Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed Dub link-management helper, but it should be reviewed because it can delete links and bundles a much broader Dub API spec with sensitive non-link operations.
Install only if you intend the agent to manage Dub links in the authenticated workspace. Use a least-privilege Dub token if available, confirm exact link IDs before delete or bulk operations, and avoid letting the skill use non-link endpoints from the bundled API reference.
The skill exposes a destructive operation where a single supplied linkId directly controls deletion. Without confirmation, validation, or ownership checks, an attacker or ambiguous prompt could abuse parameters to delete arbitrary links accessible to the token.
DELETE /links/{linkId}linkId.Bulk deletion can remove up to 100 links at once, but the skill lacks any explicit warning, confirmation requirement, or preview mechanism. This magnifies the blast radius of prompt mistakes or parameter abuse and can cause large-scale service disruption in the authenticated workspace.
Bulk delete is highly susceptible to parameter abuse because a prompt can supply many linkIds at once, causing wide-scale deletion in the authenticated workspace. The absence of preview, confirmation, or per-item validation significantly increases blast radius and abuse potential.
### 10) Bulk delete
- `DELETE /links/bulk`
- Deletes up to 100 links.
- Required query param: `linkIds`.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
{
"openapi": "3.0.3",
"info": {
"title": "Dub API",
"description": "Dub is the modern link attribution platform for short links, conversion tracking, and affiliate programs.",
"version": "0.0.1",
"contact": {
"name": "Dub Support",
"email": "support@dub.co",
"url": "https://dub.co/support"
},
"license": {
"name": "AGPL-3.0 license",
"url": "https://github.com/dubinc/dub/blob/main/LICENSE.md"
}
},
"servers": [
{
"url": "https://api.dub.co",
"description": "Production API"
}
],
"paths": {
"/links": {
"post": {
"operationId": "createLink",
"x-sp
The deep-link open tracking endpoint explicitly describes probabilistic tracking using the user's IP address but provides no explicit privacy warning in the skill context. IP-based attribution materially raises privacy sensitivity and may create compliance issues if invoked by an agent without transparent disclosure and consent.
Partner-program administration and bounty moderation capabilities allow impactful business actions such as creating partners, banning/deactivating them, issuing links, viewing partner analytics, and approving or rejecting submissions. These operations are unrelated to simple link management and could be abused to alter partner relationships, disable links, or affect payouts and program governance.
The spec includes financial and partner-program functions such as commissions, payouts, and embed token creation that are not justified by a links-management skill. If an agent can access these operations under a misleadingly narrow skill description, it could expose sensitive business data or perform high-impact administrative actions without informed user intent.
The skill is described as a Dub Links API for link CRUD/list/count/bulk operations, but the bundled OpenAPI spec exposes a much broader set of capabilities including analytics, events, customer data, partner administration, commissions, payouts, embed tokens, and bounty workflows. This creates a capability mismatch that can let an agent invoke sensitive or destructive operations outside user expectations, increasing the risk of over-privileged tool use and unintended data access or modification.
The trigger phrases are broad enough to activate the skill for generic requests like 'list links' or 'count links' without clearly requiring Dub-specific context. This increases the chance of unintended tool invocation against an external account, especially when multiple link-management contexts could exist.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
3. Generate an API key and export it in shell:
- `export DUB_API_KEY="..."`
4. Validate credentials with a Links endpoint:
- `curl -s -H "Authorization: Bearer $DUB_API_KEY" "https://api.dub.co/links/count" | jq '.'`
Useful onboarding note: if initial signup is needed, this referral can be used:
`https://refer.dub.co/agents`
No suspicious patterns detected.