Back to skill

Security audit

qa-regression-testing

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent QA regression-testing guidance skill with limited read-only tools and no evidence of hidden execution, persistence, or data exfiltration.

Installers should review the broader Kokxi/qa-test-skills package before running the unpinned npx command, especially because it may add more skills than this artifact. The reviewed skill itself is read-only guidance for regression planning and does not show hidden execution or persistence.

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 (3)

Rp1

Medium
Category
MCP Rug Pull
Confidence
92% confidence
Finding

The skill instructs users to run npx skills add Kokxi/qa-test-skills without pinning an exact package version or immutable source reference. This creates a supply-chain risk: a later package update, account compromise, or malicious republish could cause users to install unexpected code when following the documentation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The natural-language description and when-to-use field specify user utterances entirely in Chinese, which can act as a locale-specific policy constraint. The file also includes some English text, but it does not explicitly state that other languages are supported or that Chinese is required for a region-specific purpose.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The file title and introductory instructions are entirely in Chinese and provide no indication that another language can be used. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation unless the locale restriction is explicitly justified.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.