Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Alibabacloud Ecs Gpu Diagnosis

v0.0.1-beta.1

Diagnose Alibaba Cloud ECS GPU instances to detect GPU device status, driver issues, and hardware failures. Use this Skill when users report GPU instance ano...

0· 18·0 current·0 all-time
byalibabacloud-skills-team@sdk-team
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchasesRequires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill's stated purpose (diagnosing Alibaba Cloud ECS GPU instances) aligns with the commands and APIs used (aliyun ecs CreateDiagnosticReport, DescribeDiagnosticReports, DescribeInstances, DescribeRegions). However, the SKILL.md repeatedly requires an Alibaba Cloud AccessKey/CLI configuration while the registry metadata lists no required env vars or primary credential. A diagnostic skill that runs cloud APIs legitimately needs cloud credentials; failing to declare them in metadata is an inconsistency.
!
Instruction Scope
The SKILL.md instructs the agent to run aliyun CLI commands that will use the user's Alibaba Cloud credentials (via configured CLI). All referenced actions (installation guidance, region validation, instance queries, creating and polling diagnostic reports) are within the stated purpose. Still, the instructions explicitly require the user’s AccessKey and to run CLI commands; this access to cloud credentials is not documented in the skill's declared requirements, which is a scope/visibility concern.
Install Mechanism
This is an instruction-only skill (no install spec, no code files). The included installation references use official Alibaba Cloud CLI URLs hosted on aliyuncli.alicdn.com and Homebrew; those are expected and not suspicious. No arbitrary or obfuscated download hosts are present.
!
Credentials
The runtime requires the Alibaba Cloud CLI to be configured with AccessKey credentials and appropriate RAM permissions, but requires.env and primary credential fields in the registry metadata are empty. The skill therefore omits declaring sensitive credentials it will depend on; this mismatch reduces transparency and prevents automatic least-privilege checks.
Persistence & Privilege
The skill does not request permanent presence (always:false) and does not include install-time scripts, so it does not appear to request elevated persistence. However, disable-model-invocation is false (normal) which means the agent could invoke the skill autonomously; combined with access to cloud credentials (see above), autonomous invocation increases risk if you allow the agent to run without supervision.
What to consider before installing
What to consider before installing: - The skill will run Alibaba Cloud CLI commands that use your Alibaba Cloud AccessKey (configured via `aliyun configure`). The registry metadata does not declare those credentials — verify you are comfortable with an installed skill that expects to use your cloud credentials. - Prefer to run this skill only with an account or RAM user that has limited, scoped permissions (the references/ram-policies.md lists ecs:CreateDiagnosticReport, ecs:DescribeDiagnosticReports, ecs:DescribeInstances). Create a temporary or least-privilege RAM user for diagnosis rather than using owner/root credentials. - Because the skill can be invoked autonomously by the agent, avoid enabling autonomous invocation unless you fully trust the skill and the agent’s behavior. If you allow autonomous use, ensure the agent cannot access broad credentials or additional environment variables. - The CLI download URLs in the docs point to official aliyuncdn/alidn sources (alicdn), which is expected; still validate downloads yourself (checksum, official docs) before running installers. - If you need stronger assurance, request the publisher/source, a verifiable homepage or repository, or a declared required-credentials field in the metadata. Having the skill explicitly declare required env vars / primary credential (e.g., ALIBABA_ACCESS_KEY_ID/ALIBABA_ACCESS_KEY_SECRET or an authentication profile) would resolve the main inconsistency. Bottom line: functionality looks coherent for diagnosing ECS GPU instances, but the omission of declared credentials in metadata and the potential for autonomous invocation create a meaningful security/visibility gap — treat this skill with caution and use least-privilege credentials if you proceed.

Like a lobster shell, security has layers — review code before you run it.

latestvk974ss4wyfsrhbdgd2eqvxq4px84yc8p

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments