ClawHub
Back to skill

Security audit

badgebot

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent Slack lead-capture automation, but it needs review because it can move personal contact data across Slack, Apollo, and HubSpot and update CRM records with limited safeguards.

Install only if you intend to run this exact Slack-to-Apollo-to-HubSpot workflow. Use least-privilege tokens, confirm the hard-coded Slack channel, HubSpot portal, and DM recipient are correct and authorized, disable personal email/phone reveal unless approved, require review before HubSpot writes, and document how cron polling, state files, and logs will be stopped and cleaned up.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (4)

Missing User Warnings

Medium
Confidence
93% confidence
Finding
The workflow sends extracted lead data, potentially including personal email and phone details, to Apollo.io for enrichment without any consent, notice, or policy gating. This creates a real data-sharing/privacy risk because sensitive contact information from Slack posts is transmitted to a third party outside the original system context.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
Natural-language DM replies are treated as authoritative instructions to patch HubSpot records, which can let ambiguous, spoofed, or accidental messages alter CRM data. In the skill context, this is more dangerous because it directly modifies production contact records from loosely parsed chat input without a strong approval or validation step.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The documentation explicitly instructs use of Apollo options that reveal personal emails and phone numbers, but it provides no notice about privacy, consent, or data-handling requirements. In the context of a Slack-based lead capture workflow that extracts contact details from images and messages, this increases the risk of collecting sensitive personal data without adequate user awareness or lawful basis.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The notes state that enriched data auto-syncs to HubSpot, but the documentation does not warn that information retrieved from Apollo may be transmitted onward into another integrated external system. In this skill, data originates from Slack content and DMs, so silent propagation into HubSpot can expand exposure, create compliance issues, and make operators underestimate where personal data is being stored.

Static analysis

No suspicious patterns detected.