Back to skill

Security audit

Greenhouse Apply

Security checks for vulnerabilities and agentic risk

Overview

The skill is purpose-built for Greenhouse job applications, but it can access email verification codes and submit personal application data without an explicit user approval checkpoint.

Review this skill before installing if you want explicit control over job submissions. Use it only when you are comfortable giving the agent browser access, the resume path, application answers, and narrowly scoped email access for the Greenhouse verification code; manually review the completed form before any final submit action.

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
Confidence
93% confidence
Finding
The skill explicitly includes retrieving email verification codes and submitting job applications, which are privacy- and account-sensitive actions, but it provides no warning, consent checkpoint, or boundary on when those actions should occur. In this context, the skill can cause unauthorized access to a user's inbox-derived codes and submit personally identifiable information to third-party employers without clear user confirmation, making the omission materially risky.

Static analysis

No suspicious patterns detected.