Foxreach

AdvisoryAudited by Static analysis on May 10, 2026.

Overview

Detected: suspicious.exposed_secret_literal

Findings (1)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the agent misinterprets a request, it could alter or delete FoxReach records or launch outreach to many recipients.

Why it was flagged

The skill lets the agent run Python SDK calls that can delete data, bulk modify campaigns, and start outreach, but the instructions do not require confirmation, limits, or a preview before these high-impact actions.

Skill content
allowed-tools: Bash(python *), ...
| Delete | `client.leads.delete(lead_id)` |
| Start | `client.campaigns.start(campaign_id)` |
| Add Leads | `client.campaigns.add_leads(campaign_id, [lead_ids])` | Bulk add |
Recommendation

Require explicit user confirmation and a dry-run/preview for campaign start, delete, bulk add, email-account removal, and sequence/template mutations; show IDs, counts, affected accounts, and reversibility before executing.

What this means

Anyone with the API key may be able to access or modify FoxReach leads, campaigns, inbox data, and sender accounts within that workspace.

Why it was flagged

A FoxReach API key is expected for the integration and can optionally be stored by the CLI config; this is purpose-aligned but sensitive, especially because registry metadata does not declare a primary credential.

Skill content
Both use API key authentication with keys prefixed `otr_`... Always get the API key from the user or environment... config set-key --key otr_...
Recommendation

Use a least-privileged key if available, prefer secure environment or secret storage, avoid pasting keys into shared logs or chat history, and document where CLI config stores the key.

What this means

The setup may fail, or the user may end up installing unreviewed local code before giving it a FoxReach API key.

Why it was flagged

The reviewed manifest contains only documentation files and no SDK/CLI code or install spec, so this setup depends on code outside the supplied artifacts.

Skill content
The Python SDK is at `integrations/sdk-python/` and the CLI is at `integrations/cli/`... cd integrations/sdk-python && pip install -e .
Recommendation

Verify the SDK/CLI source before installing, pin or include the expected package, and add an install spec or provenance details for the referenced code.

Findings (1)

critical

suspicious.exposed_secret_literal

Location
SKILL.md:44
Finding
File appears to expose a hardcoded API secret or token.