T03 · Remote Payload Retrieval and Execution
- Location
setup/完整安裝指南-從零開始部署AI老闆助理.md:35- Finding
Unverified Remote Scripts Are Downloaded and Executed Directly
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This executive-assistant skill is mostly documented as a productivity template, but it includes high-impact setup and autonomy guidance that users should review before installing.
Install only after reviewing the setup commands, package identities, gateway service behavior, OAuth scopes, Telegram token handling, and Git backup steps. Use minimal Google scopes, avoid pipe-to-shell and unpinned global installs where possible, create .gitignore before any Git commit, require explicit confirmation before pushes or public/external actions, and disable camera/gateway/admin capabilities unless you intentionally need them.
setup/完整安裝指南-從零開始部署AI老闆助理.md:35Unverified Remote Scripts Are Downloaded and Executed Directly
setup/README-AI老闆助理安裝與設定.md:20Persistent Gateway Service Is Installed Without Adequate Hardening Guidance
SKILL.md:89Ambiguous and Unpinned Third-Party Package Installation
setup/完整安裝指南-從零開始部署AI老闆助理.md:377Sensitive Workspace Files Are Committed Before Ignore Rules Are Created
agent-persona/RULES.md:280Behavioral Rules Permit Unconfirmed Repository Pushes and Persistent State Modification
setup/完整安裝指南-從零開始部署AI老闆助理.md:475Troubleshooting Instructions May Expose the Telegram Bot Token
The phrase 'Do first, report later' explicitly encourages autonomous execution before user confirmation, which is especially risky for a skill integrated with Gmail, Calendar, Drive, and automation tooling. In this context, the agent could send emails, modify schedules, alter documents, or trigger workflows without meaningful human review, increasing the chance of irreversible or externally visible actions.
The camsnap capability enables camera footage capture, which is unrelated to the declared executive-assistant functionality and introduces serious privacy and surveillance risk. If abused, it could silently collect sensitive visual information from monitored environments and exfiltrate it through other available messaging or file tools.
The documented exec capability allows arbitrary local shell command execution, which is far beyond what an executive-assistant skill should require. If triggered by ambiguous natural-language requests or prompt injection from emails/files/web content, it could lead to command execution, local data theft, credential access, or system compromise.
The documented gateway capability permits viewing/updating gateway configuration and restarting services, giving the assistant control over core platform behavior. In the context of an executive-assistant skill, this is unjustified and dangerous because misuse could disable safeguards, alter routing, introduce persistence, or cause denial of service.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
3. **本機環境保護**
- 開啟 FileVault 磁碟加密。
- 一定要有登入密碼與螢幕鎖。
- 不要把 `credentials.json` 與 token 檔同步到公開雲端硬碟(如無加密的 Dropbox、公開 GitHub)。
---
curl ... | sudo -E bash - is a dangerous chained execution pattern because it fetches remote content and immediately executes it as root. In a setup guide for broad end-user deployment, this is especially risky because users are likely to copy-paste it without inspection, amplifying supply-chain or interception impact.
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt-get install -y nodejs
# 驗證
No suspicious patterns detected.