ClawHub
Back to skill

Security audit

HPC CalculiX

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent CalculiX finite-element workflow helper with a disclosed SLURM solver template and no evidence of hidden access, persistence, or exfiltration.

Before installing, understand that this skill may help prepare and run CalculiX jobs on a scheduler, so review generated .inp decks and SLURM scripts before submitting jobs that consume cluster time or overwrite result artifacts.

A.I.G

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

SkillSpector

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

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 44)May include surrounding context.

md
- Do not invent Abaqus-style keywords that CalculiX does not support.
- Do not mix node or element set names inconsistently across sections and steps.
- Do not define loads and boundary conditions without checking the active step type.
- Do not skip material and section coherence when the deck fails later in the solve.

## Outputs

Static analysis

No suspicious patterns detected.