Skill flagged — suspicious patterns detected

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

CloudQ

v1.0.0

CloudQ — 全球首款 ITOM 领域虾,全渠道 ChatOps、全天候 AIOps、全方位 CloudOps。当用户询问"你是谁"、"cloudq是什么"、"cloudq能做什么"、"介绍一下自己"、查看云架构、查询架构目录、获取架构详情、查看架构评估结果、查看风险评估项、巡检项、云资源风险、开通智能顾问等...

0· 43·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name, description, required env vars (TENCENTCLOUD_SECRET_ID / SECRET_KEY), and the included scripts (API signing, STS AssumeRole, role creation, login URL) are coherent with a Tencent Cloud Smart Advisor / console-login helper. The IAM operations declared (CreateRole, AttachRolePolicy, AssumeRole, etc.) align with the stated role-creation and console-login features.
!
Instruction Scope
SKILL.md and the scripts direct the agent/user to permanently write AK/SK into shell startup files and to run local Python scripts that will call Tencent Cloud APIs and may create roles. Version-check logic (check_env.py) reaches out to an external ClawHub API and includes fallbacks that invoke local CLIs or npx — this introduces remote network calls and potential code execution beyond the declared Tencent endpoints. The guidance to 'permanently write' credentials into ~/.bashrc/.zshrc is risky and broader than necessary: temporary credentials or a role-based flow would be safer. The scripts do write a local config (~/.tencent-cloudq) (role ARN only) which is consistent with the stated behavior.
Install Mechanism
No formal install spec (instruction-only style) so nothing would be installed automatically by a package manager. However, the version-check code may call 'clawhub' CLI or run 'npx' as a fallback — that can download and execute code at runtime (npx downloads packages from npm). This is a non-obvious side-effect of the version-check and increases risk because it can pull third-party code during an otherwise benign check.
!
Credentials
The skill requests only Tencent Cloud AK/SK (proportionate to its purpose). However the SKILL.md explicitly instructs users to permanently write those secrets into shell rc files — a high-risk practice. The code indicates it stores only the role ARN locally and claims temporary STS credentials are not persisted, which is good, but the permanent-credentials recommendation is unnecessary and dangerous. No unrelated credentials are requested.
Persistence & Privilege
The skill writes a local config directory (~/.tencent-cloudq) and caches account UIN; those are reasonable for this tool. It does not set always: true. It can perform IAM write operations (CreateRole/AttachRolePolicy/DeleteRole) but the scripts state these should only run after explicit user consent. Confirmed: role creation and deletion are present and require AK/SK with sufficient permissions — this elevates impact if keys provided are high-privilege.
What to consider before installing
What to consider before installing/use: - The skill is coherent with a Tencent Cloud Smart Advisor helper and legitimately needs Tencent AK/SK, but do NOT paste your long-lived SecretId/SecretKey into shell startup files as the README suggests. Prefer temporary STS tokens, least-privilege keys, or create a dedicated low-permission user for this tool. - The code's version-check can call 'npx' as a fallback. That may download and execute third-party code at runtime; if you want to avoid that, run check_env.py with --skip-update or ensure 'requests' and/or a vetted clawhub CLI are present so npx fallback is not used. - The tcloud_api module falls back to disabling TLS verification when certifi is not installed (it creates an SSL context with verify disabled). This means API calls could be made without certificate validation if certifi is missing — which can expose AK/SK to network attackers. Before use, ensure certifi is installed in the Python environment (pip install certifi) or run in an environment with a correct system CA bundle. - Review the provided scripts (create_role.py, cleanup.py, login_url.py) yourself. The role creation flows will perform CAM CreateRole/AttachRolePolicy operations that require permissions; verify the exact policies (QcloudAdvisorFullAccess, QcloudTAGFullAccess) match your security posture. - If you proceed: run the scripts in an isolated account or with a dedicated, limited-permission service account; inspect network traffic if possible; use --skip-update during checks to avoid unexpected external downloads; and delete/rotate credentials when finished. If you have low confidence in the source (homepage unknown), consider obtaining an official published integration from a trusted vendor instead.

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

aiopsvk9763w8hcdra8qzhcmmyjqc8f183jvwgchatopsvk9763w8hcdra8qzhcmmyjqc8f183jvwgcloudopsvk9763w8hcdra8qzhcmmyjqc8f183jvwglatestvk9763w8hcdra8qzhcmmyjqc8f183jvwg

License

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

Runtime requirements

☁️ Clawdis
Binspython3
EnvTENCENTCLOUD_SECRET_ID, TENCENTCLOUD_SECRET_KEY

Comments