Back to skill

Security audit

Aliyun OSS or Tencent COS oss upload online access

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marked this skill suspicious because scanners report concerns about upload visibility, credential handling, and activation scope, while one script was only partly inspected.

Consider the reported privacy and credential-handling concerns before installing. The scan is incomplete because the upload script was only partly inspected, so the available evidence cannot establish that the skill is safe; the suspicious verdict does not by itself mean the author acted maliciously.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/upload.js
Finding

Unrestricted download redirects can publish internal HTTP responses

Content
View full analysis

Impact

Internal HTTP data accessible without additional authentication can become publicly readable through the configured OSS/COS bucket. The attack requires a reachable internal endpoint and bucket permissions allowing the documented public-read upload.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Findings (15)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 28)May include surrounding context.

md
4. **唯一访问方式**:凭证**仅**由 `scripts/upload.js` 在进程内读取(env var 或 config.json)。调用方只能通过执行 `node scripts/upload.js` 完成上传,不得以其他任何方式触及凭证。

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 174)May include surrounding context.

md
4. **仅执行** `node scripts/upload.js`,由脚本内部读取 config(调用方不得读取 config)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 182)May include surrounding context.

md
cd 技能根目录/oss-upload-online-access && node scripts/upload.js <本地路径或URL> [--provider aliyun|tencent]

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 189)May include surrounding context.

md
node scripts/upload.js ./docs/report.pdf

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 192)May include surrounding context.

md
node scripts/upload.js "https://example.com/file.png"

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 195)May include surrounding context.

md
node scripts/upload.js ./image.jpg --provider tencent

Uploads make files publicly readable without disclosing the public-access setting.

High
Category
Output Handling
Confidence
94% confidence
Finding

The Aliyun upload explicitly sets 'public-read' at L498, and the Tencent upload does the same at L537. Although uploading is the script's stated purpose, making uploaded contents accessible without authentication is an additional privacy-sensitive behavior that no prompt, explanatory comment, or user-facing message discloses; printing the resulting URL does not explain its public access permissions.

Content

No source excerpt is available for this finding.

Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: env.

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding

Without declared permissions the skill's intent is opaque and cannot be validated.

Content

No source excerpt is available for this finding.

Activation includes accessing files or obtaining links without requiring an intent to upload them.

Medium
Category
Trigger Abuse
Confidence
96% confidence
Finding

Activation phrases include accessing files online or obtaining links without requiring explicit authorization to upload or publish them. An agent could therefore interpret a request to access an existing resource as permission to copy a local or remote file into publicly accessible storage.

Content

No source excerpt is available for this finding.

Conversational setup instructions encourage users to disclose cloud credentials to the agent.

Medium
Category
Data Exfiltration
Confidence
99% confidence
Finding

The setup examples explicitly encourage users to paste cloud access keys and secrets into an agent conversation. This exposes credentials to conversation history, model processing, and potentially logs or integrations, contradicting the document's own prohibition on exposing credentials; a private chat does not eliminate these risks.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
78% confidence
Finding

The caret range permits different ali-oss releases to be installed rather than fixing an audited dependency version. Without an enforced lockfile, installation can introduce an unreviewed or compromised release into a process handling cloud credentials and uploaded files; no compromised release is demonstrated here.

Content

Scanner excerpt · package.json (reported line 7)May include surrounding context.

json
"license": "MIT-0",
  "private": true,
  "dependencies": {
    "ali-oss": "^6.20.0",
    "axios": "^1.6.0",
    "cos-nodejs-sdk-v5": "^2.14.2",
    "stream-to-buffer": "^0.1.0"

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
78% confidence
Finding

The axios version range allows installation results to change without a manifest change unless a lockfile is enforced. This is a dependency reproducibility and supply-chain weakness, not proof of an exploitable Axios vulnerability in the installed application.

Content

Scanner excerpt · package.json (reported line 8)May include surrounding context.

json
"private": true,
  "dependencies": {
    "ali-oss": "^6.20.0",
    "axios": "^1.6.0",
    "cos-nodejs-sdk-v5": "^2.14.2",
    "stream-to-buffer": "^0.1.0"
  }

Unverifiable Dependency: axios has 56 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +53 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
40% confidence
Finding

OSV returned advisories for this package, but its resolved version is unknown. A package-name lookup does not establish whether the installed release is affected by those advisories.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
78% confidence
Finding

The cos-nodejs-sdk-v5 caret range can resolve to different releases across installations if dependency resolution is not locked. Because this SDK handles cloud authentication and file transfers, an unreviewed release could affect sensitive operations, although the manifest does not establish any actual compromise.

Content

Scanner excerpt · package.json (reported line 9)May include surrounding context.

json
"dependencies": {
    "ali-oss": "^6.20.0",
    "axios": "^1.6.0",
    "cos-nodejs-sdk-v5": "^2.14.2",
    "stream-to-buffer": "^0.1.0"
  }
}

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
76% confidence
Finding

The stream-to-buffer range permits patch-version changes rather than guaranteeing one reviewed dependency tree. Without an enforced lockfile, this creates a limited supply-chain and reproducibility weakness; neither malicious package behavior nor actual runtime exploitation is established.

Content

Scanner excerpt · package.json (reported line 10)May include surrounding context.

json
"ali-oss": "^6.20.0",
    "axios": "^1.6.0",
    "cos-nodejs-sdk-v5": "^2.14.2",
    "stream-to-buffer": "^0.1.0"
  }
}