T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/authorize.py:34- Finding
Overprivileged Device Authorization Scope
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent kitchen-video workflow, but it grants and uses broader Beatra account authority than the one-photo task needs and silently updates local executable files.
Install only if you are comfortable giving this package a shared Beatra device credential that can access more than kitchen-video generation and with automatic code updates enabled by default. Consider disabling auto-updates with the documented command and treating the Beatra credential as account-level access, not a single-purpose kitchen-video permission.
scripts/authorize.py:34Overprivileged Device Authorization Scope
scripts/mcp_client.py:1463Unrestricted Remote Tool Dispatch Using a Full-Scope Credential
scripts/authorize.py:340Collection and Transmission of Local Host Identification
scripts/mcp_client.py:969Silent Retrieval and Installation of Mutable Remote Code
scripts/mcp_client.py:231Unrestricted HTTPS Host in Server-Directed Photo Upload
The skill's stated listing-video purpose does not prepare users for uninstall/disconnect behavior that reads and mutates local state under ~/.beatra, inspects installed skills, revokes authorization, and removes credentials. Hidden lifecycle operations affecting local files and account state are security-relevant and should not be bundled opaquely with a simple media skill.
The skill's stated listing-video purpose does not prepare users for uninstall/disconnect behavior that reads and mutates local state under ~/.beatra, inspects installed skills, revokes authorization, and removes credentials. Hidden lifecycle operations affecting local files and account state are security-relevant and should not be bundled opaquely with a simple media skill.
The skill's stated listing-video purpose does not prepare users for uninstall/disconnect behavior that reads and mutates local state under ~/.beatra, inspects installed skills, revokes authorization, and removes credentials. Hidden lifecycle operations affecting local files and account state are security-relevant and should not be bundled opaquely with a simple media skill.
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
Referenced artifact was not completely inspected
bundled `scripts/mcp_client.py`. Do not configure a host Beatra
The document states that a single approval covers image, video, music, speech, upload, model, and task tools, which is far broader than the apartment-kitchen-tour skill’s stated one-photo-to-one-kitchen-clip purpose. This creates unnecessary privilege scope and a capability mismatch: compromising or misusing this skill could grant access to unrelated account functions beyond what the user would reasonably expect.
The skill documentation explicitly introduces access to unrelated Beatra capabilities such as music, speech, and general task tools. In the context of a narrowly scoped real-estate kitchen animation skill, exposing broader platform capabilities violates least privilege and increases the blast radius if the skill is abused or the credential is stolen.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
```
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
```
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
```
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
```
They share the one full-scope Device Token stored in
`~/.beatra/credentials.json`. Installing or switching packages must not trigger
another authorization when that credential is already valid. Do not add,
enable, trust, or configure a host Beatra Connector. Never print or move the
token into command arguments, environment variables, logs, chat, or another
The script requests an extremely broad OAuth scope set, including wallet spending, task control, voice access, and multiple generation capabilities that are unrelated to a skill described as turning one kitchen photo into a short clip. Excessive scopes violate least privilege and significantly increase blast radius if the token is misused, leaked, or if the skill behavior expands beyond the user's expectation.
The file is a generic remote MCP client with session management, tool discovery, arbitrary tool invocation, upload support, telemetry, and update logic, which is far broader than a kitchen-photo animation skill needs. That mismatch materially increases attack surface and enables the package to act as a general-purpose remote command conduit under the guise of a narrowly described media skill.
The package downloads manifests and archives and then replaces installed files on disk, effectively giving the remote service the ability to change local code after installation. Even with checksum validation, the trust root is the remote discovery channel, so compromise or misuse of that channel can push new behavior unrelated to the user-approved kitchen-tour skill.
The CLI supports listing all remote tools and calling any named tool with JSON from stdin, turning the package into a generic broker for arbitrary remote capabilities. For a skill advertised as producing a single kitchen-photo clip, this is especially dangerous because users and reviewers may not expect broad remote tool access hidden behind a domain-specific package.
The exposed update command explicitly enables self-modification of the installed package, allowing local executable code to be replaced from network-fetched content. In the context of a narrowly described kitchen-tour skill, self-modification is unjustified and materially raises the risk of post-install behavior drift or malicious code delivery via the update path.
)
update = subparsers.add_parser(
"update",
help="Check, install, or configure Beatra package self-updates",
)
update.add_argument(
"--check",
The uninstall script manages a shared Beatra device connection, inventory, and credential lifecycle, which is materially unrelated to the skill’s advertised function of generating a kitchen-photo animation. Even if framed as package cleanup, this gives the skill authority over shared authentication state for other skills, creating a risky mismatch between declared purpose and actual capability.