Back to skill

Security audit

Build Lead Scoring

Security checks for vulnerabilities and agentic risk

Overview

This is a straightforward HubSpot lead-scoring setup guide, with operational impact users should review before turning models on.

Before installing or using this skill in a live HubSpot portal, review any workflows, lists, reports, routing, alerts, and MQL handoff rules that may depend on lead scores. Test or stage changes where possible, document how to disable or revert the scoring model, and confirm with the business owner before turning scores on.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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 (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill gives step-by-step instructions to create, modify, save, and turn on live HubSpot lead scoring models, but it does not explicitly warn that these changes affect production records asynchronously and can influence downstream workflows, routing, lifecycle progression, reporting, and sales prioritization. Even though the content is operationally legitimate, enabling scoring in a live portal without a staging/sandbox check or impact warning can cause broad business-process disruption and misclassification at scale.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.