cold-email

SAFE max severity MEDIUMSkillSpector Safe 0 registry clawhub.ai last scanned 1 scan

Verdict safe, but 2 findings (2 medium), mainly data exfiltration. Most recent scan 2026-02-06.

The cold-email skill presents MEDIUM security risks primarily related to data handling and API key management. The skill transmits potentially sensitive lead data (PII, business intelligence) to a third-party service without explicit privacy disclosures or consent warnings. API key security guidance is insufficient, risking credential exposure. The skill lacks critical metadata (license, compatibility, allowed-tools) reducing transparency. Long-running sync requests (3-5 min) may cause agent timeouts and resource issues without proper async handling. Referenced files (lead.py, the.py) are missing from the package. No evidence of prompt injection, command injection, or malicious code execution was found. The skill appears functionally legitimate but requires improved security documentation and data handling transparency.

Scanner's overall assessment (LLM analyzer)

Second scanner: NVIDIA SkillSpector

Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

Generate hyper-personalized cold email sequences using AI. Turn lead data into high-converting outreach campaigns.

Package
1 file, 5.5 KB
SKILL.md
766 words, 12+ sections
Code
None. Instructions only.

SKILL.md covers: MachFive - AI Cold Email Generator · Setup · Campaign ID · Endpoints · List Campaigns (discover before generate) · Single Lead (Sync) · Batch (Async) · Lead Fields · Options · Errors · Usage Examples · Pricing

Findings

MEDIUM Hardcoded API Key Requirement Without Secure Storage Guidance Data Exfiltrationllm

The skill requires MACHFIVE_API_KEY environment variable but provides no guidance on secure storage, rotation, or scope limitations. Users may hardcode keys in shell profiles or insecure locations. The skill also accepts API keys via X-API-Key header, increasing exposure surface.

Setup instructions: 'Set `MACHFIVE_API_KEY` in your environment' and 'Or use `X-API-Key: {MACHFIVE_API_KEY}` header' without security warnings or best practices.
Remediation: Add security guidance: (1) Use secure credential managers (e.g., 1Password, AWS Secrets Manager), (2) Never commit keys to version control, (3) Rotate keys regularly, (4) Use minimum-scope API keys, (5) Warn about X-API-Key header exposure in logs/network traffic.
MEDIUM Potential Data Exfiltration via Third-Party API Data Exfiltrationllm

The skill sends potentially sensitive lead data (names, titles, emails, LinkedIn URLs, company websites) to an external third-party service (app.machfive.io) without explicit user consent warnings or data handling disclosures. Users may unknowingly transmit PII and business intelligence to an external vendor.

POST requests to https://app.machfive.io/api/v1/campaigns/{campaign_id}/generate and /generate-batch send lead objects containing: name, title, company, email, company_website, linkedin_url. No privacy notice or data handling disclosure provided.
Remediation: Add explicit warnings: (1) Disclose that lead data is transmitted to MachFive's servers, (2) Link to MachFive's privacy policy and data handling practices, (3) Warn users about GDPR/CCPA compliance requirements, (4) Recommend obtaining consent before processing personal data, (5) Document data retention and deletion policies.

What is in the package

FileKindSize
SKILL.mddoc5.5 KB

External hosts referenced

app.machfive.io acme.com linkedin.com machfive.io

Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.

Environment variables referenced

MACHFIVE_API_KEY

Package contents recorded 2026-10-22. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.

What we checked

What we did not check

Sources