Security audit
Security checks across malware telemetry and agentic risk
This appears to be a legitimate Volcengine cloud-operations bundle, but it needs Review because it combines broad cloud/database write authority with under-disclosed automatic telemetry and uneven safeguards.
Install only if you intend to let the agent operate a Volcengine account. Review and disable telemetry if unwanted, use least-privilege or temporary credentials, avoid high-privilege profiles, require explicit approval before writes/deletes, and be cautious with database service-role keys, Terraform apply scripts, --yes deployment commands, and any action involving billing, domains, IoT, security workflows, or production data.
def check_ve_login_status() -> str:
try:
completed = subprocess.run(
["ve", "sts", "GetCallerIdentity"],
check=False,
capture_output=True,`CreateVirtualNode`: - Required: `Kubeconfig`, `VirtualNodeConfig`. - This creates infrastructure and needs a cleanup plan before execution. ### VMP
- `ListPreagg` returned HTTP 200 with an empty response.
- VMP metric APIs (`QueryMetrics`, `QueryMetricsRange`, `GetLabelValues`, `GetLabels`, `GetSeries`) were validated against a temporary `vmp.standard.15d` workspace with a real remote-write sample `codex_vmp_verify_value{run_id="run_20260602_1916",source="codex"} 42`. `QueryMetrics` and `QueryMetricsRange` returned value `42`; `GetLabels` returned `__name__`, `run_id`, and `source`; `GetLabelValues` returned the test `run_id`; `GetSeries` returned the complete series. The temporary workspace was deleted afterwards and `GetWorkspace` returned `ResourceNotExist`.
- Live batch stream APIs returned permission errors after valid `StartTime`/`EndTime` parameters were supplied, confirming the earlier `InvalidParam` was only parameter-shape related.
- `CreateVirtualNode` reached VKE and requires `Kubeconfig` plus `VirtualNodeConfig`. It was not executed because it needs an external Kubernetes kubeconfig and the registry does not include a matching virtual-node delete API for cleanup.
- Most domain, IoT, trademark, metrics, sec_agent, VEEN, and Flink APIs returned `AccessDenied` for the tested account. Creating dependent resources cannot bypass IAM denial; use an account with the relevant service permissions for full business-flow testing.
Implementation notes:- `ListPreagg` returned HTTP 200 with an empty response.
- VMP metric APIs (`QueryMetrics`, `QueryMetricsRange`, `GetLabelValues`, `GetLabels`, `GetSeries`) were validated against a temporary `vmp.standard.15d` workspace with a real remote-write sample `codex_vmp_verify_value{run_id="run_20260602_1916",source="codex"} 42`. `QueryMetrics` and `QueryMetricsRange` returned value `42`; `GetLabels` returned `__name__`, `run_id`, and `source`; `GetLabelValues` returned the test `run_id`; `GetSeries` returned the complete series. The temporary workspace was deleted afterwards and `GetWorkspace` returned `ResourceNotExist`.
- Live batch stream APIs returned permission errors after valid `StartTime`/`EndTime` parameters were supplied, confirming the earlier `InvalidParam` was only parameter-shape related.
- `CreateVirtualNode` reached VKE and requires `Kubeconfig` plus `VirtualNodeConfig`. It was not executed because it needs an external Kubernetes kubeconfig and the registry does not include a matching virtual-node delete API for cleanup.
- Most domain, IoT, trademark, metrics, sec_agent, VEEN, and Flink APIs returned `AccessDenied` for the tested account. Creating dependent resources cannot bypass IAM denial; use an account with the relevant service permissions for full business-flow testing.
Implementation notes:| `ga` | `ListAccelerateAreas`, `ListBandwidthPackages`, `GetAcceleratorDimension`, related endpoint info APIs | `ListAccelerateAreas` returned real area metadata. Bandwidth/accelerator/dimension/endpoint-related APIs returned empty results, consistent with `ve ga ListAccelerators` and `ve ga ListPublicBandwidthPackages` showing zero resources. Resource-detail APIs need GA accelerator, bandwidth package, listener, or endpoint IDs. | | `live` | `DescribeLiveBatchStreamTranscodeData`, `DescribeLiveBatchStreamSessionData` | Validated through signed Action/Version calls and RFC3339 time strings. `ListDomainDetail` returned no live domains; both private stats APIs returned zero totals and empty stream lists, matching current resource state. | | `flink` | `ListGMSProject`, `ListGMCSResourcePool` | Validated with the Flink compatibility request. `ListGMCSResourcePool` returned a valid empty list; `ListGMSProject` reached Flink business logic and reported the current account is not initialized. Other GWS/GAS APIs require Flink project/resource pool/application/draft IDs and should not be called without creating those resources. | | `vke` | `ListVirtualNodes`, `CreateVirtualNode` | `ListVirtualNodes` returned an empty list, consistent with no VKE clusters. `CreateVirtualNode` reached VKE and returned missing `VirtualNodeConfig`; real validation requires an existing Kubernetes cluster/kubeconfig and cleanup plan. | | `CDN` | `DescribeOriginTopStatisticalData` | Request reached the service, but CDN is stopped/not opened for the account (`OperationDenied.ServiceStopped` / `NotFound.Service`). Positive validation requires CDN service activation and a CDN domain with origin traffic. | | `mcdn` | `DescribeCdnDomainConfig` | Service is unsubscribed (`mcdn.UnsupportedOperation.ServiceUnsubscribed`). Positive validation requires MCDN activation and a CDN domain. | | `veenedge` | `GetVEENInstanceUsage`, `GetVEEWInstanceUsage`, `GetBandwidthUsage`, `GetBillingUsageDetail` | GET request ...[truncated 25 chars]
# KMS Service Notes ## DescribeKeys Requires a Keyring `DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`.
## DescribeKeys Requires a Keyring `DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`. Observed in `cn-beijing`: `DescribeKeyrings` returned an existing keyring, `DescribeKeys` worked when scoped to that keyring, and `DescribeSecrets` returned `TotalCount: 0`.
## DescribeKeys Requires a Keyring `DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`. Observed in `cn-beijing`: `DescribeKeyrings` returned an existing keyring, `DescribeKeys` worked when scoped to that keyring, and `DescribeSecrets` returned `TotalCount: 0`.
`DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`. Observed in `cn-beijing`: `DescribeKeyrings` returned an existing keyring, `DescribeKeys` worked when scoped to that keyring, and `DescribeSecrets` returned `TotalCount: 0`. ## Deletion Is Scheduled
`DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`. Observed in `cn-beijing`: `DescribeKeyrings` returned an existing keyring, `DescribeKeys` worked when scoped to that keyring, and `DescribeSecrets` returned `TotalCount: 0`. ## Deletion Is Scheduled
`DescribeKeys` requires `KeyringName` or `KeyringID`; omitting both returns `MissingParameter`. Observed in `cn-beijing`: `DescribeKeyrings` returned an existing keyring, `DescribeKeys` worked when scoped to that keyring, and `DescribeSecrets` returned `TotalCount: 0`. ## Deletion Is Scheduled
KMS keys and secrets are not immediate-delete resources. The current action list exposes `ScheduleKeyDeletion`, `CancelKeyDeletion`, `ScheduleSecretDeletion`, and `CancelSecretDeletion`. Prefer read/help validation unless the test explicitly accepts scheduled deletion and follow-up cleanup tracking. Disposable tests should use a dedicated keyring name prefix.
If explicitly approved, record every returned resource ID, use `DeleteCluster` with an explicit retention/deletion policy, and verify `ListClusters` no longer returns the test cluster. A newly created cluster can reject deletion while its status is `Creating` or addon sync is still `Progressing`; poll `ListClusters` until the cluster reaches `Running`/`Ok`, then delete.
Observed in `cn-beijing`: clusters, node pools, kubeconfigs, and addons all returned empty lists; supported addon/resource-type discovery worked.
Validation note: a no-node Flannel cluster with `Tags: [{"Key":"publish-by","Value":"deploy-skill"}]` was created in `cn-beijing`, the tag appeared in `ListClusters`, then `DeleteCluster` removed it after the cluster reached `Running`/`Ok`.1. **Default to read-only** — unless the user explicitly requests a change, execute in read-only mode 2. **DryRun first** — if a write/destructive operation supports `--DryRun true`, run a DryRun to preview the plan, then confirm before executing 3. **Confirm before executing** — show the full command for write operations and wait for approval 4. **Protect credentials** — never read `~/.volcengine/config.json`; never expose access-key, secret-key, or session-token in output ### DryRun Notes
58/58 vendors flagged this plugin as clean.
Detected: suspicious.dangerous_exec, suspicious.exposed_secret_literal
const child = spawn("bash", [REPORTER_SH, "--mode", "skill"], {const child = spawn("bash", [REPORTER_SH, "--mode", "skill"], {password = [REDACTED]
export TF_VAR_redis_password='[REDACTED]'
export TF_VAR_redis_password='[REDACTED]'