Back to skill

Security audit

biodiversity corridor calculator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward biodiversity analysis helper that clearly uses an external API for the geospatial data it processes.

Before installing, consider whether your project locations or conservation parcels are sensitive. Use this skill only when you are comfortable sending the listed coordinates and H3 indices to the documented third-party API, and avoid submitting confidential sites unless you have permission.

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
94% confidence
Finding

The skill directs an agent to send precise geolocation data and project parcel identifiers (H3 indices) to a third-party external API, but the documentation provides no privacy notice, consent requirement, retention statement, or data-sharing limitation. This can expose sensitive project locations or conservation planning data to an external service without the user's awareness, creating confidentiality and compliance risks even if the endpoint is otherwise legitimate.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.