Skill flagged — suspicious patterns detected

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

Alicloud Compute Swas Open

v1.0.2

Manage Alibaba Cloud Simple Application Server (SWAS OpenAPI 2020-06-01) resources end-to-end. Use for querying instances, starting/stopping/rebooting, execu...

0· 1k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (manage SWAS resources) align with the included scripts and SKILL.md: the package provides SDK examples and scripts to list instances, summarize inventory, query SSH port, and run a 'fix ssh access' operation via the SWAS RunCommand API. However, the registry metadata declares no required environment variables or primary credential, while both SKILL.md and all scripts expect Alibaba Cloud credentials (ALICLOUD_ACCESS_KEY_ID / ALICLOUD_ACCESS_KEY_SECRET and optional security token and region). This omission is an inconsistency that should be corrected but does not by itself indicate malicious intent.
Instruction Scope
SKILL.md and the reference docs focus on SWAS operations (list, start/stop, command execution, firewall, snapshots, etc.). The runtime instructions and scripts only interact with the Alibaba Cloud SWAS API and instance RunCommand invocation; they do not exfiltrate data to unknown external endpoints. Note: some scripts will execute commands on target instances (fix_ssh_access modifies /etc/ssh/sshd_config and authorized_keys), which is within the stated scope but is a privileged, mutating operation and should be used with user confirmation.
Install Mechanism
There is no install spec (instruction-only for dependencies). The skill includes Python scripts that rely on the official alibabacloud Python SDK packages (alibabacloud_swas_open20200601, alibabacloud_tea_openapi, alibabacloud_credentials) referenced in SKILL.md. No downloads from arbitrary URLs or other high-risk install behavior are present.
!
Credentials
The metadata lists no required env vars or primary credential, but SKILL.md and every script call os.getenv for ALICLOUD_ACCESS_KEY_ID / ALIBABA_CLOUD_ACCESS_KEY_ID, ALICLOUD_ACCESS_KEY_SECRET / ALIBABA_CLOUD_ACCESS_KEY_SECRET, and optionally ALICLOUD_SECURITY_TOKEN. The skill legitimately needs Alibaba Cloud credentials to function; the omission in the registry metadata is an inconsistency that affects user understanding of what secrets will be required. Also, fix_ssh_access reads a local path defaulting to '~/.ssh/id_ed25519.pub' — it reads a public key file (not private key), which is reasonable but users should verify the path.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request permanent presence or attempt to modify other skills or system-wide agent settings. It will invoke API calls and RunCommand on instances, which are normal for this purpose.
Assessment
This skill appears to do what it says (manage Alibaba SWAS) and the included scripts match the documentation, but take these precautions before installing or running it: - Credentials: The registry metadata does not declare required env vars, but the code and SKILL.md expect ALICLOUD_ACCESS_KEY_ID and ALICLOUD_ACCESS_KEY_SECRET (and optionally a security token and ALICLOUD_REGION_ID). Only provide least-privilege RAM credentials needed for intended operations; prefer temporary STS tokens where possible. - Review scripts locally: fix_ssh_access modifies /etc/ssh/sshd_config (enabling PermitRootLogin yes and PubkeyAuthentication) and appends a public key to authorized_keys. That is a powerful mutating action — confirm target instance IDs and the exact public key before running. Ensure the script's --pubkey argument points to a public key file, not a private key. - Start with read-only operations: run list_instances_all_regions.py and the summary scripts first to verify credentials and scope before running any mutating actions or RunCommand invocations. - Confirm region/endpoints: SKILL.md instructs choosing the correct region and endpoint (public vs VPC). If unsure, the agent should ask you before mutating operations. - Source trust: the skill's source is listed as unknown. If you require stronger assurance, ask the author/maintainer for provenance or run the scripts in a controlled environment first. If you are comfortable reviewing the code and using least-privilege credentials, the skill is coherent with its purpose; otherwise treat it as untrusted until provenance and credential requirements are clarified.

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

latestvk976pxbyvzxpkwxn5fr86ks2j582pk3h

License

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

Comments