Back to skill

Security audit

uibc-team-law

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent UIBC legal-domain judging helper with a small local checker and no evidence of hidden access, persistence, exfiltration, or unsafe execution.

Safe to install for UIBC LAW-domain judging workflows. Users should be aware that the trigger wording is broad, so agents should apply it only when the task is actually about UIBC, TH-LAW-001, memory-transfer judging, evidence-chain evaluation, or related competition review, not ordinary legal 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 (5)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The trigger list includes broad, common terms such as “法律”, “证据包”, and “责任归属”, which can cause the skill to activate in contexts far outside its intended legal UIBC niche. Over-broad activation increases the chance that an agent invokes specialized legal/migration-identity logic on unrelated tasks, causing misrouting, policy confusion, or unsafe workflow chaining with other skills.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The description labels SKILL.md as the 'AI 调用入口' and presents it as the team instruction manual in Chinese, indicating the primary invocation surface is tied to a specific language. There is no statement that users may choose another language or that Chinese is required for a justified region-specific purpose, which can violate language/locale policy expectations.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill description lists broad trigger terms such as '法律', '证据包', and '责任归属' without clear exclusion criteria or disambiguation, which can cause the orchestrator to invoke this skill for loosely related prompts. That creates overbroad routing risk: legal-style framing or accountability language from unrelated tasks could be pulled into responses, increasing the chance of inappropriate authority, incorrect domain application, or policy bypass through misclassification.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The '何时用' section again uses broad, ambiguous activation criteria based on common terms like '法律', '迁移判定', '证据包', and '责任归属', with no gating rule to ensure the request is actually about the UIBC LAW domain. In a skill-routing system, this ambiguity can cause accidental activation on unrelated legal or evidentiary requests, leading to confused delegation and potentially unsafe or misleading outputs presented under a specialized legal authority.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

This file delegates applicability decisions to SKILL.md and does not itself define concrete scope boundaries or exclusions. In adversarial or ambiguous environments, relying on an external file for activation criteria can lead to inconsistent invocation, especially if the agent reads files partially, out of order, or if the referenced file changes independently.

Content

No source excerpt is available for this finding.