Back to skill

Security audit

Ultravibe Refactor

Security checks for vulnerabilities and agentic risk

Overview

The skill is marked suspicious because scanners found repeated use of unversioned `npx tsx` commands, which may download and run an unpinned package if it is not already installed locally.

Consider the install risk before proceeding. The evidence is incomplete because the scan was partial and several referenced paths were missing; the scanner says a pinned, locally installed `tsx` dependency would reduce the specific package-resolution risk.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (10)

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The preflight command invokes tsx through npx without specifying a version or requiring an installed local dependency. If tsx is absent locally, npx can fetch a registry-resolved version and execute it with the agent's permissions, creating a supply-chain execution risk before any preflight protection runs. This is not an MCP server reference, and a verified, locally installed, lockfile-pinned dependency would substantially reduce the risk.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The checkpoint-read command uses the same unversioned npx tsx invocation, which can resolve and execute a remote package if no local installation exists. Its apparently read-only purpose does not restrict the permissions of the package being executed; however, the supplied file does not establish whether a pinned local installation already prevents this fallback.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The timeout check can trigger execution of a registry-resolved tsx package when the local dependency is missing. A compromised resolved package would execute before the intended timeout control, so that control does not mitigate the dependency risk; an existing pinned local installation would reduce exposure.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The phase-entry gate is launched through unversioned npx tsx, allowing registry fallback if tsx is not locally installed. Malicious dependency code would run with the agent's permissions before the gate can enforce workflow constraints, although a verified lockfile-pinned local installation would mitigate this path.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

RF-1 dispatch uses an unversioned npx tsx invocation that can download and execute a registry package when the local dependency is absent. Mandatory subagent delegation does not sandbox this orchestrator-side execution, and the supplied file does not demonstrate a pinned local dependency.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

RF-1 transition relies on unversioned npx tsx, exposing it to remote dependency resolution if no local installation exists. A compromised resolved package could execute outside the intended checkpoint and baseline controls; this is the same dependency issue as the other occurrences, not a separate MCP vulnerability.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

RF-2 dispatch can execute a registry-resolved tsx version because the npx command specifies neither an exact version nor a local-only requirement. The target-file whitelist constrains the intended workflow, not arbitrary code in its launcher; exposure is lower if a verified pinned local dependency is already installed.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

RF-2 transition repeats the unversioned npx tsx dependency-resolution risk when tsx is unavailable locally. A compromised downloaded package would run with agent permissions rather than being confined by the refactoring whitelist or transition checks.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The regression-phase transition invokes unversioned npx tsx and may fetch executable package code if no local copy exists. Passing regression tests does not establish the trustworthiness of a subsequently resolved launcher dependency, though a pinned installed local copy would reduce this risk.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx tsx'.

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

The final guard-phase transition uses the same unversioned npx tsx command, permitting registry fallback when the dependency is missing. Static, test, and scope checks do not constrain arbitrary launcher-package execution, so their presence does not eliminate this conditional supply-chain risk.

Content

No source excerpt is available for this finding.