Back to skill

Security audit

Rvt To Ifc

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to do what it says: guide local RVT-to-IFC conversion, with ordinary file read/write risks for batch exports.

Install only if you intend to let the agent read RVT files and write IFC files locally. For batch conversion, use a dedicated output directory and avoid reusing output names unless you are comfortable with possible replacement by the converter tool.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
83% confidence
Finding
The markdown promotes batch processing at scale and includes examples that create output files for many RVT inputs, but it does not warn users that the operation will write large numbers of IFC files and may overwrite outputs if paths collide. Because this is a markdown file, user-facing safety disclosures about data-affecting behavior should be present when describing bulk file creation.