Back to skill

Security audit

iaiops-pharma

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a disclosed pharma/OT operations guide, but it claims the edition is read-only while also exposing a high-risk BACnet write tool for plant systems.

Review this skill carefully before installing in a live pharma or cleanroom environment. Treat it as write-capable, not read-only, and only use it where BACnet write operations are explicitly authorized, approval-gated, and blocked for cleanroom or life-safety objects unless your site procedures permit them.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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
Findings (2)

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The manifest and description repeatedly claim this pharma edition is read-only, but the documented tool surface includes bacnet_write_property, an explicitly write-capable operation. In an OT/GMP environment, this mismatch can cause an agent or operator to invoke the skill under a false safety assumption, potentially modifying cleanroom or plant-control parameters on live systems.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The documentation explicitly markets the edition as read-only, then later advertises a write path with high-risk BACnet writes, dry-run controls, and approval flow. That contradiction is dangerous because downstream automation may trust the top-level safety claim rather than the later caveat, leading to unauthorized or unsafe writes in pharmaceutical building and process environments.

Content

No source excerpt is available for this finding.