Back to skill

Security audit

Openclaw Migration Pro

Security checks for vulnerabilities and agentic risk

Overview

This migration skill handles broad private OpenClaw data and should be reviewed because it documents automatic archive sending, credential-handling conflicts, and unsafe installation examples.

Install only after reviewing exactly what will be archived and where it will be sent. Do not use default sending for private backups, do not include credentials or API keys in migration bundles, avoid pipe-to-bash and unpinned npx commands, and restore only into a controlled environment after inspecting the manifest and cron jobs.

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (5)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:101
Finding

Unverified Remote Installation Script Is Executed Directly by Bash

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:101 and MIGRATION-GUIDE.md:113
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: Critical

Vulnerable Code

bash
curl -fsSL https://openclaw.ai/install.sh | bash

Technical Analysis

The installation instructions pipe a response retrieved from an external URL directly into Bash. The effective executable payload is therefore determined at execution time rather than audit time.

The instructions do not pin a release, verify a cryptographic signature, validate a checksum, or provide an inspection step. HTTPS protects the connection under normal conditions but does not protect users if the server, hosting account, deployment pipeline, DNS/TLS trust path, or installation script is compromised.

This behavior is not required for the migration functionality itself. OpenClaw installation is a prerequisite operation and can be performed through a separately downloaded, authenticated release artifact.

Attack Path

  1. An attacker compromises the remote installation endpoint, its deployment pipeline, or another component capable of controlling its response.
  2. A user or agent follows the documented migration instructions.
  3. curl retrieves the attacker-controlled response.
  4. The shell begins interpreting the response immediately, without allowing the user to inspect or authenticate it.
  5. The payload executes commands with all privileges available to the invoking account.
  6. If the user invokes the command from an elevated shell, the payload may obtain system-wide privileges.

Impact Assessment

Successful exploitation permits arbitrary command execution with the invoking user's privileges. This can expose OpenClaw data, API credentials, SSH material, private files, agent configuration, and other resources accessible to the account. An elevated invocation could enable system-wide modification or persistence.

Remediation
View remediation

Remediation Suggestions

  1. Replace the pipeline with separate download and execution steps.
  2. Reference an immutable, versioned release artifact rather than a mutable installation URL.
  3. Publish a SHA-256 digest and a signature from a documented release-signing key.
  4. Require users to verify both the signature and digest before execution.
  5. Allow users to inspect the downloaded script locally.
  6. Do not recommend elevated execution unless a specific operation demonstrably requires it.
  7. Provide package-manager installation instructions with locked versions where possible.

Example hardened workflow:

bash
curl -fSLo install-openclaw.sh \
  https://example.invalid/releases/v3.1.0/install-openclaw.sh

echo "EXPECTED_SHA256  install-openclaw.sh" | sha256sum -c -
less install-openclaw.sh
bash install-openclaw.sh

T05 · Unauthorized Access and Privilege Escalation

Error
Location
SKILL.md:67
Finding

Sensitive Migration Archive Is Documented as Being Transmitted by Default

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:67-85
Vulnerability Type: Default transmission of sensitive user data without a separate opt-in action
Risk Level: High

Vulnerable Code

bash
# Package all data (default ZIP format + automatic sending)
openclaw-migration-pro pack --output ~/openclaw-pack.zip

# Output:
# Packaging OpenClaw...
# Packaging Skills...
# Packaging Memory...
# Packaging configuration...
# Packaging Cron...
# Compressing as zip...
# Package complete: ~/openclaw-pack.zip
# Sending file to the current channel...

The documented option is an opt-out rather than an opt-in:

text
--no-send: Disable automatic sending

Technical Analysis

The Skill states that its default packaging workflow automatically sends the resulting archive to the current channel. The same document says the package can contain memory, locally created Skills, OpenClaw configuration, workspace instructions, and cron jobs.

A current conversational channel is not necessarily an appropriate backup destination. It may include other participants, server-side retention, application logs, automated integrations, or infrastructure outside the user's direct control. The documentation does not identify the destination, encryption status, recipient authorization, retention policy, or file-size handling before transmission.

Sending should require a distinct affirmative action. Making sensitive transmission the default violates least-privilege and data-minimization principles. The bundled scripts/analyze.sh does not implement this feature, so the actual destination and safeguards cannot be validated from the submitted source.

Attack Path

  1. A user invokes the documented default pack command without --no-send.
  2. The tool collects private memory, Skills, configuration, workspace rules, and scheduled-task definitions.
  3. The collected data is compressed into a migration archive.

...[truncated 685 chars]

Remediation
View remediation

Remediation Suggestions

  1. Make packaging local-only by default.
  2. Require an explicit --send option and a fully specified destination.
  3. Display the destination, recipients, archive manifest, archive size, and excluded sensitive paths before requesting confirmation.
  4. Require an interactive confirmation unless an explicit noninteractive authorization flag is supplied.
  5. Encrypt archives locally before any transmission, using a recipient-controlled key.
  6. Apply deny-by-default exclusions for credentials, environment files, private keys, tokens, certificates, and channel configuration.
  7. Add tests proving that sensitive files cannot enter the archive through symlinks, alternate names, nested paths, or configuration mistakes.
  8. Document retention and deletion behavior for both local and remote copies.

T05 · Unauthorized Access and Privilege Escalation

Error
Location
PROMOTION-v3.md:33
Finding

Project Documentation Explicitly Promotes Packaging API Credentials

Content
View full analysis

Vulnerability Details

File Location: PROMOTION-v3.md:33, with corroborating statements at PROMOTION-v3.md:142-170, RELEASE-NOTES-v3.md:27,81,104,147, and RELEASE-CHECKLIST.md:25-26
Vulnerability Type: Unnecessary collection and transfer of reusable secrets
Risk Level: Critical

Vulnerable Code

text
Pack everything that's yours (including API keys)

Additional documented v3 behavior includes:

text
Pack credentials/ (your identity)

The release material also describes the backup layout as containing:

text
credentials/        Your API keys

Technical Analysis

The v3 material intentionally changes the design from excluding credentials to packaging them. API keys and tokens are authentication factors, not ordinary user data. Copying them into a general migration archive expands their exposure to local archive storage, removable media, cloud synchronization, SSH destinations, channel uploads, backups, and recipient machines.

This behavior exceeds the minimum privileges required for migration because credentials can be provisioned independently on the destination through a secret manager or destination-side configuration process. It also directly contradicts SKILL.md and MIGRATION-GUIDE.md, which claim that API keys are excluded. Users therefore cannot determine which security policy the project actually follows.

The repository does not include the advertised pack implementation, so no enforceable credential exclusion, archive encryption, access control, or cleanup mechanism can be verified.

Attack Path

  1. A user follows the v3 documentation and invokes the migration packaging workflow.
  2. The workflow includes credentials/ and potentially environment files containing API keys or tokens.
  3. The archive is copied through removable media, cloud storage, SSH, or the documented automatic channel-send behavior.
  4. An attacker obtains the archive from local s ...[truncated 664 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove credentials, tokens, private keys, certificates, environment files, and channel authentication data from all default and full-backup modes.
  2. Reconcile SKILL.md, migration guides, release notes, checklists, and promotional content around one deny-by-default policy.
  3. Provision secrets independently on the destination through a password manager, operating-system keychain, hardware-backed store, or dedicated secret-management service.
  4. If an exceptional secret-export feature is retained, make it a separate command with explicit per-secret selection, strong recipient-key encryption, warnings, and no channel-upload support.
  5. Generate and display an archive manifest that marks sensitive classifications before creation.
  6. Add automated tests that fail when files under credentials/, .ssh/, or matching secret patterns enter a normal migration archive.
  7. Document immediate credential rotation procedures for any archive suspected of exposure.

T09 · Insecure Skill Coding Practices

Error
Location
EXCLUDE-STRATEGY.md:180
Finding

Credential Backup Guidance Leaves an Unprotected Plaintext Secret File

Content
View full analysis

Vulnerability Details

File Location: EXCLUDE-STRATEGY.md:180-193
Vulnerability Type: Plaintext sensitive-data storage and unsafe temporary-file lifecycle
Risk Level: High

Vulnerable Code

bash
cat > ~/api-keys-backup.txt << EOF
openai.api_key=sk-xxx
claude.api_key=sk-xxx
github.token=ghp_xxx
EOF

# Encrypt and save
gpg -c ~/api-keys-backup.txt

The restoration example is:

bash
gpg -d ~/api-keys-backup.txt.gpg | while read line; do
  openclaw config set $line
done

Technical Analysis

The instructions first write all API credentials to a normal plaintext file in the user's home directory and only then create an encrypted copy. Encrypting the file does not delete the original plaintext. No restrictive umask, explicit file mode, isolated temporary directory, cleanup step, or secure lifecycle guidance is provided.

Depending on the user's environment, the plaintext file may be readable by other local processes, indexed, synchronized, included in backups, captured by endpoint software, or recoverable after ordinary deletion. It also aggregates multiple reusable secrets into one predictable location.

The unquoted expansion in openclaw config set $line can additionally split values on whitespace or shell glob characters, although the primary confirmed issue is plaintext secret exposure.

Attack Path

  1. A user follows the documented backup procedure.
  2. API keys and tokens are written to ~/api-keys-backup.txt.
  3. GPG creates a separate encrypted file but leaves the plaintext source in place.
  4. A local process, backup service, synchronization client, malware instance, or another account with sufficient filesystem access reads or copies the plaintext file.
  5. The attacker uses the recovered tokens against their respective services.

Impact Assessment

Exposure grants the attacker whatever privileges are assigned to the OpenAI, Claude, GitHub, and o ...[truncated 202 chars]

Remediation
View remediation

Remediation Suggestions

  1. Prefer a password manager or dedicated secret-management system instead of file-based export.
  2. If file-based encrypted export is unavoidable, use umask 077 before creating any file.
  3. Stream secrets directly into an encryption process so an intermediate plaintext file is not created.
  4. Use recipient-key encryption rather than a weak or reusable passphrase.
  5. Store encrypted output outside automatically synchronized or broadly backed-up directories unless that behavior is intentional.
  6. Avoid command-line secret values where they may be retained in shell history or process metadata.
  7. Parse restored key/value records safely rather than passing an unquoted composite string to a command.
  8. Document revocation and rotation procedures after suspected exposure.

A safer conceptual pattern is:

bash
umask 077
generate-secret-export | gpg --encrypt --recipient USER_KEY_ID \
  --output api-keys-backup.txt.gpg

T08 · Insecure Dependencies

Error
Location
README.md:24
Finding

Installation Instructions Execute Unpinned Third-Party Packages

Content
View full analysis

Vulnerability Details

File Location: README.md:24; additional occurrences include SKILL.md:258, MIGRATION-GUIDE.md:263-264,310, and PROMOTION-v3.md:23,39,112,185,213,228,252
Vulnerability Type: Unpinned dependency retrieval and execution
Risk Level: High

Vulnerable Code

bash
npx clawhub install openclaw-migration-pro

Other examples follow the same pattern:

bash
npx clawhub install openclaw-migrate-v3
npx clawhub install just-note --force
npx clawhub install skill-creator --force

Technical Analysis

The documentation uses npx to resolve and execute a package without pinning an exact version or validating package integrity and provenance. The executed code can therefore change after this audit. A compromised registry account, malicious future release, package takeover, dependency confusion condition, or altered transitive dependency can result in arbitrary code execution.

The repository also refers to placeholder source locations such as github.com/your-org/..., preventing users from reliably correlating the registry package with an auditable source release.

Repeated use of --force further reduces user control by allowing replacement of existing installations without first reviewing differences.

Attack Path

  1. An attacker gains control of the referenced registry package, a dependency, or the package publication process.
  2. The attacker publishes a malicious version under the unpinned package name.
  3. A user runs the documented npx clawhub install command.
  4. The resolver selects the current mutable package version.
  5. Package CLI code, lifecycle hooks, or transitive dependency code executes under the user's account.
  6. The payload reads or modifies files accessible to that account, including OpenClaw configuration and migration data.

Impact Assessment

Exploitation can provide arbitrary code execution with the invoking user's privileges. The p ...[truncated 208 chars]

Remediation
View remediation

Remediation Suggestions

  1. Pin every package to an exact reviewed version.
  2. Publish and verify registry integrity hashes or signed provenance attestations.
  3. Link to a real, immutable source repository and signed release tag.
  4. Lock and audit transitive dependencies.
  5. Avoid --force unless the user explicitly approves replacement after reviewing the affected files.
  6. Disable or strictly review package lifecycle scripts where supported.
  7. Document the expected package publisher, checksum, signing identity, and release artifact.
  8. Run installation with ordinary user privileges and within the narrowest practical sandbox.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
Findings (68)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · CAPABILITY-REPORT.md (reported line 33)May include surrounding context.

md
- 识别 Skill 与 Memory 目录的关联关系
- 统计 Memory 文件数和大小
- 统计 Cron Jobs 数量
- 检查敏感信息(credentials、.env 等)
- 生成 MANIFEST.json

**输出示例**:

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · DEEP-ANALYSIS.md (reported line 165)May include surrounding context.

md
- 识别 Skill 与 Memory 目录的关联关系
- 统计 Memory 文件数和大小
- 统计 Cron Jobs 数量
- 检查敏感信息(credentials、.env 等)
- 生成 MANIFEST.json

**输出示例**:

Credential Access

High
Category
Privilege Escalation
Confidence
90% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · CAPABILITY-REPORT.md (reported line 155)May include surrounding context.

命令:

bash
openclaw-migration-pro transfer --input ~/packs/ --target user@new-pc:~/
openclaw-migration-pro transfer --input ~/packs/ --target user@host:~/ --ssh-key ~/.ssh/id_rsa

工作流程:

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

curl -fsSL https://openclaw.ai/install.sh | bash fetches executable content from the network and immediately runs it. If the server, CDN, DNS, TLS termination, or distribution pipeline is compromised, arbitrary commands can be executed on the target machine.

Content

Scanner excerpt · MIGRATION-GUIDE.md (reported line 113)May include surrounding context.

bash
# 1. 安装 OpenClaw(如果未安装)
curl -fsSL https://openclaw.ai/install.sh | bash

# 2. 归位
openclaw-migrate-v2 unpack --input ~/openclaw-pack/

Chaining Abuse

High
Category
Tool Misuse
Confidence
97% confidence
Finding

The | bash chaining removes the opportunity for users or tooling to inspect the fetched content before execution. In this context, the command is presented as part of a migration workflow, which increases risk because users may run it while handling valuable local state and backups.

Content

Scanner excerpt · MIGRATION-GUIDE.md (reported line 113)May include surrounding context.

bash
# 1. 安装 OpenClaw(如果未安装)
curl -fsSL https://openclaw.ai/install.sh | bash

# 2. 归位
openclaw-migrate-v2 unpack --input ~/openclaw-pack/

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · DEEP-ANALYSIS.md (reported line 374)May include surrounding context.

md
"credentials/"
  "*.key"
  "*.pem"
  "*.env"
  ".git/"
  "node_modules/"
  "completions/"

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · OPTIMIZATION-COMPLETE.md (reported line 19)May include surrounding context.

md
"credentials/"
  "*.key"
  "*.pem"
  "*.env"
  ".git/"
  "node_modules/"
  "completions/"

YARA rule 'backdoor_persistence': Backdoor persistence with malicious payloads (shell commands, SSH key injection, hidden root users) [malware]

High
Category
YARA Match
Confidence
75% confidence
Finding

YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).

Content

Scanner excerpt · OPTIMIZATION-COMPLETE.md (reported line 202)May include surrounding context.

~/openclaw-pack/

text

**总时间**: ~5 分钟(包括网络传输)

---

### 场景 2: 增量备份

```bash
# 每天执行
openclaw-migrate pack --incremental ~/packs/base/ --output ~/packs/daily/

# 自动传输
openclaw-migrate transfer --input ~/packs/daily/ --target user@backup:~/

总时间: ~30 秒(只有变化的文件)


场景 3: 定时备份

bash
# 添加到 crontab
0 3 * * * openclaw-migrate pack --versioned --output ~/daily-backup/

# 或使用 OpenClaw Cron
openclaw cron add --name "daily-backup" --schedule "0 3 * * *" \
  --command "openclaw-migrate pack --versioned --output ~/daily-backup/"

📋 排除内容清单

✅ 打包的内容

类型位置说明
工作区 Skillsskills/workspace/本地创建的
ClawHub Skillsskills/clawhub/可重新安装
Memorymemory/所有日记、笔记
配置config/openclaw.json + 工作区配置
**C

Missing User Warnings

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The release notes explicitly promote packing credentials/ and describe API keys as part of the migration payload, but provide no warning about secret handling, encryption, access control, or disclosure risk. In the context of a migration tool, normalizing bulk export of credentials materially increases the chance of credential theft, accidental sharing, or insecure storage during transit.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The examples instruct users to transfer packed data to another system with rsync and similar workflows, while the package is said to include credentials and identity data. Without warnings about secure transport, host trust, archive protection, and exposure of secrets on remote endpoints, the documentation encourages potentially unsafe movement of sensitive material.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

The declared description promises a migration tool that analyzes an OpenClaw environment, discovers associations between Skills and their data, and supports full migration. In contrast, the provided code chunk only sets some directory variables, creates an output directory, and writes a hardcoded MANIFEST.json containing empty arrays and default values. Although the script labels itself as an analysis step, it performs no actual scanning of ~/.openclaw or the workspace, computes no file counts or sizes, and discovers no associations. This is a material description-to-behavior mismatch: the implemented behavior is a placeholder/bootstrap step rather than real environment analysis or migration.

Content

No source excerpt is available for this finding.

Ssd 3

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill states that backup archives are automatically transmitted to the current channel by default, and those archives include user memory and workspace contents. This is a direct data-exfiltration risk because backups aggregate high-value information into a single artifact and send it outside the local environment without strong user acknowledgment.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The documentation instructs users to execute a remote installation script via curl ... | bash, which runs network-fetched code immediately without prior inspection or integrity verification. This is a classic remote code execution and supply-chain risk if the server, network path, or script distribution is compromised.

Content

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

bash
# 1. 安装 OpenClaw(如果未安装)
curl -fsSL https://openclaw.ai/install.sh | bash

# 2. 归位
openclaw-migration-pro unpack --input ~/openclaw-pack/

Chaining Abuse

High
Category
Tool Misuse
Confidence
99% confidence
Finding

The | bash chaining pattern removes the user's opportunity to inspect the fetched script and directly executes whatever content is returned. In the context of a migration skill, this is especially risky because users may run it on systems containing sensitive backups and configuration data.

Content

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

bash
# 1. 安装 OpenClaw(如果未安装)
curl -fsSL https://openclaw.ai/install.sh | bash

# 2. 归位
openclaw-migration-pro unpack --input ~/openclaw-pack/

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The restore example presents openclaw-migrate unpack as a normal test command but does not warn that it restores files, configuration, and scheduled jobs onto the local system. Users may run it in the wrong environment or on a trusted assumption, leading to unintended overwrites, persistence via cron, or restoration of unsafe configuration.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
90% confidence
Finding

The document instructs users to run npx clawhub without pinning a version, which can fetch and execute whatever package version is current at install time. In a migration tool context, that creates a significant supply-chain risk because the fetched code may run with access to local files, configuration, and environment data involved in migration.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
95% confidence
Finding

The example implementation uses npx clawhub@latest inspect, which explicitly opts into executing the newest published version from the registry. That is dangerous for a tool handling environment migration because a compromised or breaking upstream release could alter behavior or execute malicious code during analysis.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The installation and usage section gives direct analyze/pack/unpack commands without clearly disclosing that the tool performs broad environment migration, including restoring configuration and cron jobs. In security-sensitive contexts, omission of that warning increases the chance of unsafe execution and social-engineering style misuse of a powerful administrative tool.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
90% confidence
Finding

The installation command npx clawhub install openclaw-migrate-v2 does not pin the package manager helper version, leaving execution dependent on whatever clawhub version is resolved at runtime. Because this skill performs broad migration and restore actions, any compromised helper version could directly affect system files and restored artifacts.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The documented unpack flow performs system-modifying actions including restoring files, restoring cron jobs, and automatically running npm dependency installation, but it does not mention any confirmation, dry-run mode, or review step before execution. In a migration tool, this increases the risk of unsafe or unintended changes on the target host, especially if the backup contents are untrusted or stale.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

The transfer feature describes automated rsync/SSH transmission of backup contents to another machine without clearly warning that user data, memory files, and configuration artifacts will leave the local host. Even when SSH is encrypted, users still need notice about what categories of potentially sensitive data are being transmitted.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The unpack examples show restore commands without warning that they may overwrite, merge into, or otherwise modify files in the destination environment. For a migration tool, this can lead to accidental destructive changes or corruption if users run restore operations on the wrong host or into an existing installation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The document explicitly recommends transferring and cloud-sharing migration archives but does not warn that those archives may contain sensitive configuration, credentials, tokens, personal data, or other environment-specific secrets. In the context of an environment migration tool, users may reasonably assume the archive is safe to upload or share, increasing the risk of unintended data exposure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The report describes unpack/restore behavior as successful completion but does not warn that restoring an archive can overwrite existing skills, memory, config, or cron data in the target environment. In a migration tool, omission of overwrite/restore safety guidance increases the chance of accidental destructive changes or unsafe restoration from untrusted archives.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The report recommends the tool can be confidently published for user use while describing creation of archives containing skills, memory, config, and cron data, yet provides no privacy, retention, or secure-handling warning. Backup archives commonly contain sensitive operational and personal data, so encouraging distribution without data-handling guidance can lead to unintended exposure during storage, transfer, or sharing.

Content

No source excerpt is available for this finding.