Back to skill

Security audit

IR35 Status Assessment

Security checks for vulnerabilities and agentic risk

Overview

This is a plain Markdown IR35 assessment skill with no code, install hooks, persistence, or hidden data access.

Reasonable to install from a security perspective. Users should remember that contract text and working-practice details can be commercially sensitive, and the output should be treated as an assessment aid rather than definitive legal or tax advice.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The invocation description is broad enough to match generic requests such as wanting to 'understand employment status', which can cause the skill to activate when the user did not explicitly ask for an IR35 assessment. In an agent setting, over-broad triggering can lead to unintended collection or processing of sensitive contract and tax information, and may steer conversations into legal-tax guidance without clear user intent.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
98% confidence
Finding

The rule "UK English throughout" imposes a specific language/locale choice as a hard requirement. The policy allows locale constraints when the user is offered a choice or when the constraint is clearly documented and justified as region-specific; here the file is UK-specific in subject matter, but it still instructs output language rigidly without user opt-in.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.