T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/huawei_cloud/dispatcher.py:1469- Finding
Read-only Skill exposes destructive Huawei Cloud administration actions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill presents itself as read-only impact analysis, but its bundled dispatcher exposes destructive CCE and Kubernetes operations plus risky credential handling.
Review this skill before installing. Use only narrowly scoped read-only Huawei Cloud IAM and Kubernetes RBAC credentials, and do not expose production write-capable credentials to its dispatcher unless the package is changed to remove or block all mutation and secret-export actions.
scripts/huawei_cloud/dispatcher.py:1469Read-only Skill exposes destructive Huawei Cloud administration actions
scripts/huawei_cloud/auto_remediation.py:150Auto-remediation action can replace production Deployment templates
scripts/huawei_cloud/network.py:670TLS certificate verification is disabled for authenticated cloud and Kubernetes requests
scripts/huawei_cloud/cce_k8s.py:55Kubernetes client private keys are written to predictable temporary files
scripts/huawei_get_node_security_groups.py:136Standalone helper transmits an access-key identifier as an IAM authentication token
The file exposes extensive destructive and administrative capabilities such as deleting clusters, deleting nodes, scaling workloads, hibernating clusters, and modifying networking, which are far beyond the stated purpose of dependency-impact analysis. In an analysis-focused skill, these write operations materially increase blast radius and create a path for accidental or unauthorized destructive actions under the guise of diagnostics.
The secret-listing function can enumerate Kubernetes Secrets and optionally return their raw data, which is unrelated to dependency-impact analysis and directly enables credential/material disclosure. Because Secrets often contain tokens, passwords, certificates, and keys, this creates a high-value exfiltration path.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: dependency-impact-analyzer
description: Use this skill when a Huawei Cloud CCE incident needs service topology impact analysis, including Service/Ingress/Pod/Node propagation paths, upstream/downstream blast radius, affected entrypoints, and a complete Markdown impact report with evidence and confidence limits.
---
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Inspecting node security groups and VPC rules is outside the declared Service/Ingress/Pod/Node dependency-reporting scope. This is another overprivilege indicator that can reveal infrastructure security posture while users believe they are running a narrowly targeted analyzer.
Detected: suspicious.exposed_secret_literal, suspicious.insecure_tls_verification