MoreLogin
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill mostly matches its stated MoreLogin-management purpose, but it exposes broad account/device-changing API access with unclear guardrails.
Install only if you intentionally want an agent to manage MoreLogin profiles and cloud phones. Before using it, confirm the API base URL is localhost, review any generic API calls, and require explicit approval for deletes, cache clearing, ADB/device actions, proxy changes, or batch edits.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked incorrectly, the agent could make broad changes to the user's MoreLogin account resources, not just run the safer documented workflows.
This exposes a raw endpoint/method/body passthrough to the MoreLogin Local API rather than only scoped subcommands. In a skill that can delete profiles, clear caches, edit cloud phones, and manage proxies/tags, the generic mode broadens what the agent may call without documented endpoint allowlisting or approval gates.
Use API mode when a dedicated subcommand is not yet implemented:
node bin/morelogin.js api --endpoint /api/env/page --method POST --data '{"page":1,"pageSize":20}'Require explicit user confirmation for all write/delete/batch calls, add endpoint allowlists for generic API mode, and provide dry-run or recovery guidance where possible.
A user or agent could potentially run commands on a cloud phone through the API path, which is more powerful than ordinary profile management.
The contract documents a cloud-phone command-execution endpoint even though other docs say direct cloudphone exec was removed. Combined with generic API mode, this leaves unclear whether device command execution is actually blocked.
### `POST /api/cloudphone/exeCommand` - Body: - `id` (int64) required - `command` (string) required
Remove this endpoint from AI-facing docs or explicitly denylist it in generic API mode unless the user gives a clear, specific command-execution approval.
MoreLogin profile, proxy, tag, and cloud-phone API requests could be redirected away from the expected local endpoint if the environment variable is present.
The code allows the API destination to be changed by an undeclared environment variable, while the skill documentation emphasizes the official localhost API. If set unexpectedly, requests and payloads could be sent somewhere other than the intended local service.
const DEFAULT_BASE_URL = process.env.MORELOGIN_LOCAL_API_URL || 'http://127.0.0.1:40000';
Declare this configuration option, default to localhost, warn on non-local URLs, and require explicit user approval before using a non-local API base URL.
Commands can affect real browser profiles, cloud phones, proxies, groups, tags, and cached session data in the logged-in account.
The skill operates through the user's already logged-in MoreLogin desktop session. That is purpose-aligned and disclosed, but it means the agent acts with the user's MoreLogin account authority.
Requirements: MoreLogin Desktop `v2.15.0+`, logged-in local account
Use the skill only with the intended MoreLogin account, verify target IDs before write/delete actions, and review changes after execution.
Users have less provenance information for deciding whether to trust the skill package.
The registry metadata does not identify an upstream source or homepage for a Node-based CLI skill that controls a local account/device API. The included package-lock reduces dependency ambiguity, but provenance is still limited.
Source: unknown Homepage: none
Prefer packages with a verifiable source repository/homepage, and inspect the installed files before granting access to a logged-in MoreLogin environment.