skills
- Type
- Plugin
- Scanned
- Nov 13, 2026
- Version
- 79a788a4f8b0
- Files read
- 70
This plugin connects AI coding agents to Momentic's cloud and local tools to write, run, and maintain browser and mobile tests and run exploratory QA sessions. Its biggest risk is that its local MCP servers run npx -y in the active project folder and omit version pins in several agent configs, so a crafted node_modules folder in a cloned repository or a compromised upstream release can run arbitrary code on your machine.
What it can reach
- Network
- Connects to Momentic's hosted MCP server (mcp.momentic.ai) and API (api.momentic.ai), downloads CLI packages from npm and cli.momentic.ai, and can open qa tunnel connections exposing local or private web apps to Momentic's cloud QA service.
- Files
- Reads and edits repository test files (*.test.yaml, *.module.yaml, momentic.config.yaml), saves downloaded run archives, screenshots, and QA reports, and uploads mobile app builds, git patches, or test fixtures when requested.
- Secrets
- Reads MOMENTIC_API_KEY and saved Momentic CLI credentials, reads Momentic test environment variables, and can pass user-provisioned .env files, environment variable names, or browser auth-state files to QA sessions.
- Shell commands
- Spawns npx on startup to download and run local Momentic MCP servers, and instructs the coding agent to run qa, momentic, momentic-mobile, git, curl, jq, and unzip CLI commands.
- Browser
- Automates local or cloud browsers to preview, run, and debug end-to-end web tests through the momentic MCP server and CLI.
- System
- Interacts with local Android emulators or devices (via adb and ANDROID_HOME) and iOS simulators (via Xcode) when authoring or running mobile tests.
Findings
-
HighLocal MCP launcher resolves binaries from the workspace node_modules on startup
When the plugin starts, local-mcp.cjs (as well as the npx commands in .codex-mcp.json, .cursor-mcp.json, and .devin-plugin/plugin.json) spawns npx in the current project directory without an isolated --prefix. Because npm exec checks the working directory's node_modules tree before downloading from npm, cloning an untrusted repository that contains a committed node_modules/momentic (with matching version 3.73.0 in Claude Code, or any version in Codex, Cursor, and Devin) causes the plugin to execute the repository's binary automatically at startup with MOMENTIC_API_KEY in its environment, before the user runs npm install or asks the AI to do anything.
Fix: Bundle the pinned Momentic MCP packages inside the plugin directory (or pass an isolated user-owned --prefix directory to npm exec) and invoke the binary from that isolated path while keeping cwd set to the project directory so momentic.config.yaml is still found.
-
MediumUnpinned npm packages are auto-downloaded and executed at startup in Codex, Cursor, and Devin
While Claude Code's .mcp.json enforces exact CLI versions through local-mcp.cjs, .codex-mcp.json (along with .cursor-mcp.json and .devin-plugin/plugin.json) launches npx -y momentic mcp and npx -y momentic-mobile mcp with no version pin. On a cold start or cache refresh, npx silently downloads and runs whatever latest version is currently on npm, exposing the user's machine and MOMENTIC_API_KEY to a compromised package release without an explicit plugin update.
Fix: Pin exact package versions (such as momentic@3.73.0 and momentic-mobile@1.46.0) across .codex-mcp.json, .cursor-mcp.json, and .devin-plugin/plugin.json, or ship the dependencies inside the plugin with a lockfile.
-
MediumSkill instructs the agent to pipe an unpinned remote install script into sh
skills/mo-qa/references/installation.md:10
When the qa CLI is missing, the mo-qa skill directs the agent to references/installation.md (also duplicated in claude/skills/mo-qa/references/installation.md), which tells it to run curl -fsSL https://cli.momentic.ai/qa | sh (or npm install -g qa@latest). Piping an unpinned remote script directly into sh runs arbitrary code without version pinning, checksum verification, or signature checks, even in the hosted-only claude/ plugin variant whose README states it includes no local scripts.
Fix: Pin a release version and verify a published cryptographic checksum or signature before executing any downloaded installer, or ask the user to install the qa CLI manually.
