Back to skill

Security audit

Product Differentiation Amazon

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local Amazon product strategy analyzer with a disclosed but unpinned global install command users should treat cautiously.

Install only from a trusted npm/GitHub context, avoid running the install command with administrator privileges, and prefer a pinned or locally reviewed installer if reproducibility matters. The skill itself appears to process user-supplied product and review data locally.

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

Unpinned npm Package Execution During Global Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 15–17
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Medium

Vulnerable Code

bash
npx skills add nexscope-ai/eCommerce-Skills --skill product-differentiation-amazon -g

Technical Analysis

The documented installation command invokes the skills npm package through npx without specifying an exact version or verifying an integrity hash. If the package is not already available locally, npx may retrieve its currently resolved version from the configured npm registry and execute its CLI code.

Consequently, the code executed during installation is not fully determined by the audited repository. A compromised package release, registry account, dependency, or registry configuration could cause the command to execute code that differs from the version originally reviewed.

The global installation option (-g) further increases the potential scope by installing remotely sourced content into a persistent, system-wide or user-wide package location.

Attack Path

  1. An attacker compromises the npm package, one of its transitive dependencies, its publisher account, or the package source resolved under the name skills.
  2. The attacker publishes a malicious version containing harmful CLI or lifecycle behavior.
  3. A user follows the installation command in SKILL.md.
  4. Because no exact package version is specified, npx resolves and downloads the attacker-controlled release.
  5. npx executes the package with the permissions of the invoking user.
  6. The malicious package may modify local files, access data available to that user, or alter the globally installed Skill content.

Impact Assessment

Successful exploitation could provide arbitrary code execution with the privileges of the user running the installation command. Accessible resources may include the user's files, environment variables, development c ...[truncated 431 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin the installer to a specific, reviewed package version, for example:
    bash
    npx --yes skills@<audited-version> add nexscope-ai/eCommerce-Skills --skill product-differentiation-amazon
    
  2. Verify the selected package version and its dependency tree before publishing the installation instructions.
  3. Use a lockfile and npm integrity metadata where installation workflow permits.
  4. Document the expected npm registry and prevent resolution through untrusted registry mirrors.
  5. Avoid global installation by default. Prefer a project-local or isolated installation with least-privilege permissions.
  6. Run installation without administrator or root privileges.
  7. Consider distributing a reviewed local installer or signed release artifact whose integrity can be independently verified.
  8. Periodically audit the installer package and all transitive dependencies for ownership changes, unexpected lifecycle scripts, and known vulnerabilities.
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Rp1

Medium
Category
MCP Rug Pull
Confidence
89% confidence
Finding

The installation command uses npx skills add ... without pinning an exact package/version, which can cause users to execute whatever version is currently resolved at install time. If the upstream package, dependency chain, or package name resolution is compromised, users could run unreviewed code during installation in a security-sensitive context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

This file contains natural-language behavior that defaults to a specific language/locale (en) unless --zh is explicitly supplied. Under the policy, forcing a language without user opt-in can be a locale policy violation when no neutral language-selection flow is provided.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.