Back to skill

Security audit

perplexity-search

Security checks for vulnerabilities and agentic risk

Overview

This skill is coherent for paid Perplexity web search, but it depends on mutable external installs and remote skill definitions before handling wallet-funded paid calls.

Review the SELAT CLI package version and the installed perplexity-search SELAT skill before use. Do the free dry run first, confirm the quoted USDC cost, avoid sudo/global installs where possible, and only fund or run paid escalations when the exact endpoint behavior is visible and acceptable.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:64
Finding

Unpinned Global Installation of an Executable npm Dependency

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 64
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: Medium

Vulnerable Code

bash
selat --version || npm install -g @selat-ai/selat-cli

Technical Analysis

The documented setup command globally installs the latest release of @selat-ai/selat-cli without specifying an audited version, integrity digest, lockfile, or verifiable package provenance. The installed dependency's implementation is not included in this project and therefore could not be audited.

npm packages may execute lifecycle scripts during installation. Because the package is installed globally, such scripts and the installed executable run with the permissions of the invoking user and can affect locations outside the project directory. The unpinned package reference is mutable: following the same instruction later may retrieve different code than the code originally reviewed.

This is a supply-chain weakness rather than evidence that the named package is currently malicious. Exploitation would require compromise or malicious replacement of the package, its publisher account, or its distribution path.

Attack Path

  1. An attacker compromises the npm package, its publisher account, or a relevant distribution channel.
  2. The attacker publishes a malicious release under the existing package name.
  3. A user follows the documented setup command while the selat executable is unavailable.
  4. npm resolves the unversioned dependency to the attacker-controlled release.
  5. Malicious lifecycle scripts may execute during installation, or malicious behavior may execute when the installed CLI is subsequently invoked.
  6. The payload runs under the invoking user's privileges and may interact with the same environment later used for wallet initialization and paid operations.

Impact Assessment

Successful exploitation could provide arbitrary code execution w ...[truncated 617 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to a specific audited version, for example:
    bash
    npm install -g @selat-ai/selat-cli@<audited-version>
    
  2. Publish and verify package integrity and provenance information, including npm provenance attestations and expected distribution hashes where practical.
  3. Avoid global installation where possible. Use a project-local, locked dependency or execute it in an isolated container or restricted environment.
  4. Commit a lockfile when adopting a project-local installation so dependency resolution remains reproducible.
  5. Disable npm lifecycle scripts during installation when compatible with the package, then explicitly perform only reviewed setup actions.
  6. Document that users must not run the installation as root or through sudo.
  7. Pin the separately downloaded perplexity-search skill by immutable version and digest, and make its exact reviewed manifest and escalation documentation available with this project.
  8. Establish a dependency-update process that audits each new CLI and transitive-dependency release before changing the pinned version.
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 (1)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 124)May include surrounding context.

md
its `SKILL.md` ("Escalations") and `references/endpoints.md` — which carry the