Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Huawei MaaS usage reporter that uses cloud credentials for read-only statistics queries, with some credential-storage and package-source cautions.
Install only if you intend to query Huawei Cloud MaaS usage and are comfortable letting the script read Huawei credentials from environment variables or a user-specified credentials file. Prefer temporary or least-privilege read-only IAM credentials, protect any credential file with restrictive permissions, and choose the pip package index/mirror deliberately before installing dependencies.
The skill describes capabilities to read environment variables and files and to make outbound network requests, but it does not declare an explicit tool scope such as allowed-tools or permissions. That creates an authorization gap where the runtime may permit broader-than-intended access, increasing the chance of unintended credential/file exposure or unreviewed network activity.
Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.
> **⚠️ Important: Handling user-provided credentials**
>
> If a user attempts to provide AK/SK directly (e.g., "my AK is xxx, SK is yyy"):
> 1. **Stop immediately** — Do not execute any commands
> 2. **Politely refuse** and return the following message:
> ```
> For account security, please do not provide Huawei Cloud Access Key ID and Access Key Secret directly in the conversation.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
2. **1b. Resolve time range** — Parse `--from` / `--to` (YYYY-MM-DD), or map user expression ("last 7 days" / "last 14 days" / "last 30 days" / "this month") to a rolling/calendar window
3. **1c. Auto-segment** — If time range exceeds 30 days, split into multiple ≤ 30-day segments and aggregate results
4. **1d. SDK sign request** — `Signer(_Creds(ak, sk)).sign(sdk_request)` — AK/SK in Python process memory only
5. **1e. POST ShowStatistics** — `requests.post("https://modelarts.{region}.myhuaweicloud.com/v1/{project_id}/maas/monitoring/show-statistics", headers=signed_headers, data=body_bytes)`
6. **1f. Aggregate & convert** — Sum segment results; convert token unit (thousand → M tokens, actual = value × 1000)
7. **1g. Print table** — Output Total Tokens / Prompt Tokens / Completion Tokens / Total Requests / Total Errors / Error Rate + Period
The guide conditionally switches pip to a Huawei Cloud mirror based only on the host timezone, which changes the software supply source without explicit user consent. This can cause users outside a trusted enterprise environment to install packages from an unexpected index, weakening supply-chain transparency and increasing the risk of tampered, stale, or policy-noncompliant dependencies if that mirror is compromised or not appropriate for the user.
Line L275 states that AK/SK stays exclusively in Python process memory and 'never in ... environment variables (read-only access)'. However, multiple earlier sections explicitly require reading AK/SK from environment variables (HW_ACCESS_KEY / HW_SECRET_KEY) as a primary authentication method. This is an internal documentation contradiction about how credentials are handled.
The guidance states that the script should always use the OS local timezone and explicitly says to never hardcode alternatives such as CST or Asia/Shanghai. This is a natural-language locale policy constraint, and the document does not present it as a user choice or justify it as a region-specific compliance requirement.
The manifest describes a skill for querying MaaS token and request/error statistics, but the code also implements a general-purpose local file read path for secrets via --credentials-file. While credential use is expected for calling Huawei Cloud APIs, arbitrary local file access is an extra capability not stated in the manifest's user-facing purpose.
This code accepts a credentials file and parses access key, secret key, and security token values from it, which is a sensitive operation involving credential material. While the module docstring documents environment-variable usage, there is no user-facing warning or disclosure around storing or supplying long-lived credentials via a local file.
No suspicious patterns detected.