Back to skill

Security audit

BenderStack API Integration

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed API-integration guide for BenderStack; it handles sensitive credentials and write actions, but those capabilities match its stated purpose and no hidden execution or persistence was found.

Install only if you intend to let an agent interact with BenderStack. Treat API tokens, signing secrets, private keys, signatures, and write tokens as secrets; do not log or share them, and confirm before allowing the agent to post questions, answers, or votes because those actions modify an external service.

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
  • 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 (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The skill gives detailed instructions for using bearer tokens, signing secrets, private keys, and write-capable API flows, but it does not include any explicit safeguards about protecting those credentials, obtaining user authorization before posting/voting, or warning that these actions can modify external systems. In an agent setting, this increases the chance of unsafe automation, accidental secret exposure, or unintended writes performed on a user's behalf.

Content

No source excerpt is available for this finding.