T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:20- Finding
Automatic Installation and Updating of Unpinned Executable Plugins
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for managing Alibaba Cloud MongoDB, but it asks users to run mutable CLI/plugin installation steps and handle powerful cloud credentials and destructive database operations.
Install only if you need broad Alibaba Cloud MongoDB administration. Use a dedicated RAM user with the smallest permissions needed, avoid auto plugin updates where possible, verify CLI/plugin provenance before installing, avoid entering real secrets in agent-visible commands, and require explicit review before deletion, password reset, public endpoint, billing, KMS, or backup-retention changes.
SKILL.md:20Automatic Installation and Updating of Unpinned Executable Plugins
references/cli-installation-guide.md:20Unverified Privileged Installation of Mutable Latest CLI Packages
references/cli-installation-guide.md:128Cloud Access Keys, Tokens, and Database Passwords Passed Through Exposed Process Channels
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
> Cross-region lookup scripts and full-region scan scripts: see [references/operations.md § Query Regions and Instances](references/operations.md)
Referenced artifact was not completely inspected
| [references/related-apis.md](references/related-apis.md) | Complete API and CLI command list with external documentation links |
Documenting the permanent-destruction API without a safety warning exposes an especially dangerous irreversible capability with no contextual guardrails. In a skill intended for automation, omission of warnings around permanent destroy operations materially raises the risk of catastrophic data loss.
Including KMS key creation, listing, description, and deletion introduces powerful cross-service cryptographic administration unrelated to normal MongoDB lifecycle management as described. If exposed through the skill, an agent could create or destroy keys affecting other services, causing confidentiality loss or operational outages well beyond MongoDB.
The billing API capability to create standalone KMS service instances is unrelated to MongoDB management and materially expands the skill into paid cross-service provisioning. This can lead to unauthorized spend, shadow infrastructure creation, and abuse of billing-authorized credentials.
The examples actively instruct operators or agents to create KMS keys and KMS instances, normalizing unrelated high-privilege actions inside a MongoDB skill. Example code is especially dangerous because it is likely to be copied directly into automation, turning scope creep into executable behavior.
The trigger phrase "list instances" is overly generic and can activate this skill for unrelated requests that merely mention listing instances. In this skill, accidental activation is more dangerous than usual because the skill is capable of high-impact cloud operations such as deletion, password reset, public exposure, and billing changes, so misrouting a conversation into this skill increases the chance of unintended administrative actions.
The trigger phrase "reset password" is extremely broad and can match unrelated account-recovery requests outside this specific service. Because this skill includes a root password reset workflow for MongoDB instances, unintended activation could steer an agent toward changing database credentials for the wrong system, creating service disruption or unauthorized lockout.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
> [3] Reset both (execute twice separately)
> ```
>
> Determine execution count based on user's answer; **do NOT auto-execute twice without user confirmation**
>
> **Password rules:** 8-32 characters, must contain at least three of: uppercase letters/lowercase letters/digits/special characters (`!@#$%^&*()_+-=`)
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
[MUST] Before modifying whitelist:
- First query current whitelist (
describe-security-ips) and display to user- Ask for modification mode: Cover (overwrite, ⚠️ deletes existing IPs) / Append (add, errors on duplicate IPs) / Extend (extend, recommended)
- Do NOT use Cover mode without asking the user
aliyun dds describe-security-ips --db-instance-id <id> --user-agent AlibabaCloud-Agent-Skills/alibabacloud-mongodb-instances-manage
This guide is for installing and configuring the general Aliyun CLI and includes broad cross-service administration material unrelated to MongoDB instance management. In an agent skill scoped to MongoDB lifecycle operations, this unnecessary breadth expands the operational surface and can enable or normalize actions against unrelated Alibaba Cloud services.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
tar -xzf aliyun-cli-macosx-latest-amd64.tgz
./aliyun version
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
### Linux
> **Note:** Package manager installation (`dpkg`/`rpm`/`yum`) requires root privileges. Run as root or prepend your preferred privilege escalation method.
**Debian/Ubuntu (dpkg)**
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
### Linux
> **Note:** Package manager installation (`dpkg`/`rpm`/`yum`) requires root privileges. Run as root or prepend your preferred privilege escalation method.
**Debian/Ubuntu (dpkg)**
No suspicious patterns detected.