Security audit

Alibabacloud Pts Ops

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed Alibaba Cloud load-testing helper; it needs careful cloud permissions and test-data handling but shows no hidden or malicious behavior.

Install only if you intend to manage Alibaba Cloud PTS tests. Use a least-privilege RAM user or temporary role, confirm every target and load setting before starting, test only systems you own or are authorized to test, avoid real secrets or personal data in scenarios, and treat debug logs as sensitive.

SkillSpector

By NVIDIA

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Context-Inappropriate Capability

Medium

Confidence: 91% confidence
Finding: The guide recommends installing broad Alibaba Cloud plugins such as ECS, VPC, and RDS even though the skill is scoped to PTS stress-testing. In an agent-driven context, this expands available capabilities beyond intended scope and can enable unnecessary cloud resource discovery or administration if the agent follows the documentation.

Context-Inappropriate Capability

Low

Confidence: 85% confidence
Finding: The authentication verification workflow uses ECS inspection commands like `aliyun ecs describe-regions`, which are unrelated to PTS scenario management. While not directly harmful, this normalizes broader cloud enumeration and can cause agents to exercise permissions outside the declared purpose of the skill.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The reference includes example stress-test payloads containing a token field and other sensitive-looking values without any warning not to use real secrets in load tests. In a performance-testing skill, users often copy examples directly into scenarios, so this can encourage unsafe handling of credentials and tokens that may be logged, stored in test artifacts, or sent at scale to external systems.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The POST example shows a password-bearing login request body but does not warn against using real credentials in a load-testing scenario. Because load-testing tools commonly capture request bodies, logs, exports, and reports, copied real usernames and passwords could be broadly exposed or repeatedly transmitted to external endpoints.

Missing User Warnings

Medium

Confidence: 96% confidence
Finding: The document explicitly recommends using `--log-level debug` and states that output includes request/response headers and body content, but it does not warn that these logs may contain sensitive material such as authentication headers, API parameters, internal URLs, cookies, or test payload data. In a cloud operations and stress-testing context, users are likely to run these commands against real environments, making accidental credential or data exposure through terminal history, shared logs, or CI artifacts a realistic risk.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.