Back to skill

Security audit

React Component Review

Security checks for vulnerabilities and agentic risk

Overview

This is a local React component review skill with a disclosed optional cloud CLI setup, and no hidden execution or data collection was found.

Safe to install for local component review. Before enabling the optional Ritual Cloud path, consider pinning the CLI version, avoid running it with administrator privileges, and review what the CLI will access or send during initialization.

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:94
Finding

Unpinned Global Installation of a Third-Party CLI

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 94
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: Medium

Vulnerable Code Snippet:

markdown
To enable Ritual Cloud: `npm install -g @ritualai/cli` → `ritual init` → `ritual status`.

Technical Analysis

The optional upgrade instructions direct users to install @ritualai/cli globally without specifying a reviewed version or verifying package integrity. Consequently, npm resolves the package version associated with the mutable default distribution tag at installation time rather than a version examined during this audit.

An npm installation may execute package lifecycle scripts. The global installation option also modifies the user's environment outside the project directory. If the package, one of its transitive dependencies, or its package-registry distribution channel were compromised, installation could execute attacker-controlled code with the permissions of the invoking user.

The subsequent ritual init command may initialize an external service integration in the current workspace. The audited instructions do not explain its network activity or identify what workspace information it may process. No evidence establishes that the named package is currently malicious; this finding concerns the unsafe, unpinned installation pattern and its supply-chain exposure.

Attack Path

  1. An attacker compromises the package, a transitive dependency, a maintainer account, or the relevant registry distribution tag.
  2. A user follows the documented npm install -g @ritualai/cli instruction.
  3. npm resolves and downloads the compromised release because no audited version or integrity value is specified.
  4. Malicious package code can run during installation through lifecycle scripts or when the installed CLI is invoked.
  5. The user runs ritual init and ritual status, potentially giving the compromised CLI acce ...[truncated 986 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin the CLI to a specifically reviewed release, for example @ritualai/cli@<audited-version>, rather than relying on a mutable distribution tag.
  2. Record and verify the expected package integrity digest and provenance before installation.
  3. Prefer a project-local, lockfile-controlled dependency over a global installation so the resolved dependency graph is reproducible and changes remain scoped to the project.
  4. Where compatible with the package, disable npm lifecycle scripts during installation and explicitly run only the required reviewed entry point.
  5. Document the CLI's expected network connections, authentication behavior, files accessed or created, and data transmitted by ritual init and ritual status.
  6. Advise users not to run the installation or initialization commands with administrator privileges.
  7. Re-audit the pinned package and its transitive dependencies before recommending it as part of the skill workflow.
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