Back to skill

Security audit

Ultravibe Bugfix

Security checks for vulnerabilities and agentic risk

Overview

The skill is rated suspicious because its instructions repeatedly use `npx tsx`, which may download and run an unpinned package if it is not already installed; the scan could not review related dependency files.

Consider waiting to install until you can confirm that `tsx` is pinned in a reviewed dependency lockfile and that the workflow uses that local installation. The scan covered the one reported Markdown component, but reference resolution was partial and dependency controls were unavailable, so the evidence is incomplete.

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

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

This is a conditional dependency supply-chain risk, not an MCP server reference: npx tsx can download and execute an unpinned package when a suitable local installation is unavailable. Running it as the initial preflight check means package execution occurs before the workflow's checks can provide protection; no dependency manifest or lockfile was supplied to establish whether local resolution mitigates this.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The checkpoint command uses npx tsx without establishing a pinned local dependency. If tsx is missing locally, npx may fetch and execute a registry-resolved version with the agent's permissions; the checkpoint-reading purpose does not restrict that executable's privileges. The MCP label is inaccurate, and project dependency controls could mitigate the risk but are not available for review.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

Although this command implements a timeout safeguard, its npx tsx launcher can resolve an unpinned registry package if no suitable local installation exists. A compromised resolved package could execute before the timeout safeguard runs. This is a conditional dependency-execution issue rather than an MCP configuration issue.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The phase-entry gate relies on an unversioned npx tsx invocation, which can download a package when the local executable is absent. Consequently, the gate does not itself protect against a compromised launcher executing with agent permissions. Existing locked local dependencies could reduce this risk, but they were not provided; the reference is not an MCP server.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The BF-1 dispatch command repeats the conditional supply-chain exposure from npx tsx: without a suitable local installation, it can fetch and execute an unpinned package. Subagent delegation does not sandbox the launcher or prevent it from accessing the orchestrator's resources. The static finding's MCP terminology is incorrect.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The BF-1 transition uses an unpinned npx launcher that may execute a registry-resolved tsx package if local resolution fails. A compromised launcher would run before transition validation and could act outside the intended artifact and checkpoint restrictions. This is a dependency risk, not evidence of a malicious MCP server.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

BF-2 dispatch invokes npx tsx without showing that a pinned local version is required. When tsx is absent locally, registry fallback can introduce unreviewed executable code; the workflow's file whitelist does not constrain the launcher's process privileges. The MCP classification is inaccurate, and unseen dependency controls could mitigate this conditional exposure.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The BF-2 transition repeats the same unpinned dependency-launch pattern rather than introducing a separate attack mechanism. If npx downloads tsx, a compromised resolved package could execute with agent permissions before any transition checks. A locked local installation may mitigate this, but none is established by the supplied file; this is not an MCP reference.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The reverse-verification dispatch command can execute an unpinned tsx package through npx if no suitable local package is available. Delegating verification to a subagent does not protect against compromise of the dispatch launcher itself. The finding identifies a conditional supply-chain weakness, although its MCP server label is incorrect.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The BF-3 transition again uses npx tsx without an explicit version or local-only requirement. If local resolution is unavailable, package download and execution can occur before artifact or citation checks, so those checks do not mitigate launcher compromise. This is not an MCP server declaration, and a preinstalled locked dependency could reduce the exposure.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

The global-guard transition still relies on the same potentially registry-resolved tsx launcher. Static, test, and scope checks do not sandbox a compromised executable that runs them, so the guard context does not eliminate this conditional supply-chain risk. The command is a TypeScript runner invocation, not an MCP server reference.

Content

No source excerpt is available for this finding.

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

Medium
Category
MCP Rug Pull
Confidence
84% confidence
Finding

Even the reporting transition invokes npx tsx, which can fetch an unpinned package when a suitable local dependency is absent. Its reporting role does not restrict the launcher's access to the repository or other resources available to the agent. This is another occurrence of the same conditional dependency risk, not an MCP configuration vulnerability.

Content

No source excerpt is available for this finding.