T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/authorize.py:31- Finding
Poster Skill Requests Excessive Shared Device-Token Permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly matches its poster-design purpose, but it grants broad shared Beatra authority and silently self-updates executable files by default.
Review before installing. Only proceed if you are comfortable granting this skill a shared Beatra device authorization that covers more than poster images and if default silent updates from Beatra/CDN are acceptable in your environment. Consider disabling automatic updates with the documented update command and revoking the device in the Beatra Console when you no longer use it.
scripts/authorize.py:31Poster Skill Requests Excessive Shared Device-Token Permissions
scripts/mcp_client.py:969Default Silent Updater Replaces Executable Skill Files from a Remote Trust Chain
The skill asks for audio, voice, speech, music, and video generation permissions even though its description is limited to posters, flyers, banners, and social graphics. In context, these extra media scopes are unjustified and materially expand what a stolen or misused token can do.
A poster-design skill should not implicitly include uninstall logic, credential revocation, installed-skill inventory inspection, and deletion/modification of files under ~/.beatra without very clear separation and disclosure. These account and package-management actions are powerful local-state operations that, if misused or triggered unexpectedly, can disrupt other installations, remove credentials, or alter the host environment.
A poster-design skill should not implicitly include uninstall logic, credential revocation, installed-skill inventory inspection, and deletion/modification of files under ~/.beatra without very clear separation and disclosure. These account and package-management actions are powerful local-state operations that, if misused or triggered unexpectedly, can disrupt other installations, remove credentials, or alter the host environment.
A poster-design skill should not implicitly include uninstall logic, credential revocation, installed-skill inventory inspection, and deletion/modification of files under ~/.beatra without very clear separation and disclosure. These account and package-management actions are powerful local-state operations that, if misused or triggered unexpectedly, can disrupt other installations, remove credentials, or alter the host environment.
Referenced artifact was not completely inspected
Use only this Skill's bundled `scripts/mcp_client.py` for every remote MCP
Referenced artifact was not completely inspected
Use only this Skill's bundled `scripts/mcp_client.py` for every remote MCP
Referenced artifact was not completely inspected
Use only this Skill's bundled `scripts/mcp_client.py` for every remote MCP
Referenced artifact was not completely inspected
Use only this Skill's bundled `scripts/mcp_client.py` for every remote MCP
Referenced artifact was not completely inspected
[workflow](references/workflow.md).
Referenced artifact was not completely inspected
[workflow](references/workflow.md).
Referenced artifact was not completely inspected
- Installation registration: [installation registration](references/installation-registration.md)
Referenced artifact was not completely inspected
- Installation registration: [installation registration](references/installation-registration.md)
Automatic download, extraction, verification, and replacement of installed package files is a context-inappropriate capability for a content-generation skill and materially increases the attack surface. If the update channel, identity binding, or replacement logic is ever compromised, the skill becomes a vehicle for arbitrary code or behavior changes on the host under the guise of poster generation.
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 OAuth scope string requests broad capabilities far beyond the advertised poster-design function, including artifacts, tasks, video, music, speech, voices, and wallet access. This violates least privilege and means that any compromise, misuse, or unexpected code path using the shared credential could exercise unrelated high-value permissions.
The skill asks for audio, voice, speech, music, and video generation permissions even though its description is limited to posters, flyers, banners, and social graphics. In context, these extra media scopes are unjustified and materially expand what a stolen or misused token can do.
The CLI exposes self-update functionality that ultimately rewrites the installed package on disk, which is a form of self-modification. In the context of a poster-design skill, self-modifying behavior is especially sensitive because it is outside core functionality and creates a powerful mechanism for post-install code changes if the update channel or operational controls are compromised.
)
update = subparsers.add_parser(
"update",
help="Check, install, or configure Beatra package self-updates",
)
update.add_argument(
"--check",
Referencing credentials.json as part of the state the script may remove indicates the skill has awareness of and authority over shared credential material. In a poster-design context, access paths to credential storage are over-privileged and create unnecessary exposure to token theft, misuse, or destructive credential invalidation if the package is compromised.
#: these and then removes the directory only if it is empty — the script
#: never recursively deletes a directory it does not fully understand.
_STATE_FILES = (
"credentials.json",
"installation.json",
"host.json",
"skills.json",
The _device_token function reads an access token from credentials.json so the script can authenticate a revocation request. Direct handling of bearer tokens inside a content-creation skill is highly sensitive because compromise of the package or misuse of the function exposes authentication material and enables unauthorized calls against shared device authorization.
def _device_token(state_dir: Path) -> str | None:
path = state_dir / "credentials.json"
try:
value = json.loads(path.read_text(encoding="utf-8"))
except (OSError, ValueError):
No suspicious patterns detected.