alibabacloud-dataphin-skills

该 skill 的能力总体与“配置 Dataphin 数据质量规则”目的相符，且数据流主要指向官方 Dataphin/阿里云接口，整体不像恶意或越权型 skill。主要风险来自 standalone 模式下明确关闭 TLS 校验并携带云凭证发请求，这会显著放大中间人和凭证泄露风险；其次是官方但不够稳健的 curl|bash/自动插件更新安装链。因此结论为 SUSPICIOUS 而非 MALICIOUS：用途一致，但存在中等偏高的安全风险。

SUSPICIOUS: the core purpose and Alibaba Cloud capabilities are coherent, and the main network/data flows appear to go to official Alibaba endpoints. However, the skill includes notable security risks: official but mutable curl|bash and auto-plugin-update install paths, explicit TLS verification bypass for self-signed setups, and transitive installation/use of another skill. This looks like a legitimate cloud workflow skill with medium security risk, not confirmed malware.

该 skill 的能力与“只读 Dataphin 资产查询”目的基本一致，数据流主要指向官方阿里云 API，未见明显凭证窃取或越权写操作。主要风险来自官方但未固定的下载/插件更新链、跨 skill/插件信任扩展，以及 SDK 示例关闭 TLS 校验；因此应判为可疑但非恶意。

No direct evidence of embedded malware in the provided text (it is installation guidance), but it contains meaningful supply-chain and operational security risk patterns: direct execution of a remotely fetched installer script, downloading “latest” binaries/archives without checksum/signature pinning, and passing the access-key secret via command-line arguments. Additional risk exists because the document instructs plugin install/update, delegating further execution to downloaded plugin code managed by the CLI.

No clear evidence of embedded malware, backdoor, or intentional supply-chain sabotage in the provided fragment. The template appears to be a legitimate SDK-based wrapper for Dataphin KG schema actions. However, it introduces two notable security risks: it disables TLS certificate verification (runtime.ignore_ssl=True), increasing MITM exposure, and it prints full API responses that may contain sensitive exported schema YAML to stdout/logs. Treat this as an operational hardening concern rather than a confirmed malicious payload.

No direct malicious payload is evident in the provided fragment (it is installation/usage documentation), but it carries elevated supply-chain risk due to a remote download-and-execute installer pattern and runtime plugin installation/update. Recommended mitigations include verifying installer and archive integrity (hash/signature), pinning versions instead of ‘latest’, and restricting/monitoring plugin update sources. Malware indicators specifically (exfiltration/backdoor/persistence) are not present in this fragment alone.