Back to skill

Security audit

Ultravibe Feature

Security checks for vulnerabilities and agentic risk

Overview

The skill was marked suspicious because repeated `npx tsx` commands may download and run an unpinned package, while the scan was only partially complete.

Consider postponing installation until you can confirm that `tsx` is pinned and installed from a lockfile, so the commands cannot fetch missing tooling implicitly. The scan did not report clear malicious behavior, but it was incomplete because many referenced paths were unavailable.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (13)

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

Medium
Category
MCP Rug Pull
Confidence
80% confidence
Finding

This is a conditional dependency-resolution vulnerability, not an MCP server reference: npx tsx can download and execute a registry package when no local installation is available. The skill does not require a lockfile-backed installation or prohibit downloading missing tools, so its initial security check could itself execute an unreviewed dependency with the agent's permissions.

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 command uses the same potentially registry-resolved npx tsx dependency as the initial check. Although this is not an MCP server and a locally installed, locked dependency would mitigate the issue, that prerequisite is not established in the supplied skill; an untrusted package could execute before checkpoint validation.

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 invoke a registry-fetched tsx package if the tool is not installed locally. This is a dependency supply-chain concern rather than an MCP configuration issue, and execution occurs before the intended timeout safeguard can take effect.

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 command relies on npx tsx without establishing a pinned local installation. If registry resolution occurs, compromised dependency code would run before the phase gate; the gate does not protect against its own execution environment.

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 FE-1 dispatch command repeats the same conditional supply-chain exposure: npx may resolve and execute an unpinned registry package when tsx is absent locally. Subagent delegation does not mitigate code execution in the parent process used to generate the dispatch brief.

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 FE-1 transition command uses potentially registry-resolved tsx to enforce workflow advancement. If no pinned local installation exists, compromised package code could execute with the agent's permissions before transition validation; this is the same root issue as the other npx occurrences.

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 FE-2 dispatch step may execute a registry-fetched tsx package because the skill does not require a pinned local dependency. The intended use is ordinary development orchestration, but test and scope restrictions do not sandbox the launcher or prevent dependency code from accessing the agent's environment.

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 FE-2 transition repeats the unpinned npx resolution risk rather than referencing an MCP server. A preinstalled, lockfile-controlled tsx would mitigate it, but the supplied instructions do not establish that condition, leaving possible execution of unreviewed dependency code.

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 FE-3 dispatch command has the same conditional package-fetch exposure as earlier phases. Its verification role does not make the launcher trustworthy: a malicious resolved dependency could execute before the reverse-verification work is delegated.

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 FE-3 transition uses npx without requiring a pinned local tsx installation, allowing registry resolution when the tool is missing. This creates a conditional arbitrary-code-execution path through the toolchain, independent of the workflow's citation-validation safeguards.

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 FE-4 transition repeats the same dependency-resolution weakness; it is not a separate MCP-server vulnerability. If tsx is not installed locally, npx can execute a registry-fetched version with access to the working environment, regardless of whether semantic comparison is otherwise correctly enforced.

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 transition also depends on potentially registry-resolved tsx without an established pinned installation. The global guards and rollback policy do not contain malicious launcher code running with the agent's permissions, although a locked local toolchain would mitigate this exposure.

Content

No source excerpt is available for this finding.

The skill defines inputs and checkpoint resumption but does not specify when it should be invoked.

Low
Category
Trigger Abuse
Confidence
88% confidence
Finding

The input section accepts a generic user description and directs resumption when a checkpoint exists, without defining an explicit feature-development invocation condition. It does not distinguish requests to implement a feature from requests merely to discuss or review one, leaving activation scope ambiguous.

Content

No source excerpt is available for this finding.