telegram-pairing-customization

ISSUES FOUND max severity CRITICALSkillSpector Safe 7 registry clawhub.ai last scanned 1 scan

7 findings (1 critical, 2 high, 2 medium, 2 low), mainly resource abuse, policy violation, command injection. Most recent scan 2026-02-07.

CRITICAL SECURITY RISK: This skill performs dangerous system-level modifications to installed Node.js packages without proper safeguards. The primary threat is arbitrary code modification of the OpenClaw application through direct file manipulation using sed. The skill requires elevated privileges, lacks proper validation and error handling, and could leave the system in an inconsistent state. The modification approach is fragile and will be overwritten by application updates. This skill should NOT be used in its current form. Users should instead request this feature through proper OpenClaw development channels or use configuration-based customization if available.

Scanner's overall assessment (LLM analyzer)
Findings7
Critical1
High2
Medium2
Low2
Analyzersstatic llm meta

Second scanner: NVIDIA SkillSpector

VerdictSafe 7
Score7 / 100
Issues1
CategoriesTrigger Abuse
Version2.12.0 (static)

The two scanners disagree: Cisco rates this CRITICAL and SkillSpector found nothing. Check the false-positive register; signature matches on documentation are the usual cause. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message before approval. Use when users need to repeatedly access pairing codes after the initial request, ensuring consistent access to pairing instructions even if the initial code was missed or lost.

Package
2 files, 7.5 KB
SKILL.md
392 words, 11 sections
Code
Shell (1)

SKILL.md covers: Telegram 配对消息持续响应技能 · 概述 · 何时使用此技能 · 执行步骤 · 方法 1: 使用自动化脚本（推荐） · 方法 2: 手动修改 · 3. 重启服务 · 工作原理 · 验证修改 · 注意事项 · 故障排除

Findings

CRITICAL Arbitrary File Modification of System Node.js Package Command Injectionllm

The skill modifies a critical system file (/usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js) without proper authorization checks. This constitutes arbitrary code modification of an installed system package, which could compromise the integrity of the OpenClaw application and potentially introduce security vulnerabilities or backdoors.

scripts/apply-pairing-fix.sh

ORIGINAL_FILE="/usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js"
cp "$ORIGINAL_FILE" "$BACKUP_FILE"
sed 's/if (created) {/if (code) {/' "$ORIGINAL_FILE" > "$ORIGINAL_FILE.tmp" && mv "$ORIGINAL_FILE.tmp" "$ORIGINAL_FILE"
Remediation: 1. Never modify system-installed packages directly. 2. Use proper extension/plugin mechanisms provided by the application. 3. Implement configuration-based changes rather than code modification. 4. Require explicit user confirmation before modifying system files. 5. Validate file integrity and permissions before modification. 6. Consider using patch files with checksums instead of direct sed replacements.
HIGH Privilege Escalation Risk via System Directory Write Access Resource Abusellm

The script requires write access to /usr/lib/node_modules/, which typically requires root/sudo privileges. The skill does not validate permissions or warn users about privilege requirements, potentially leading to failed executions or encouraging users to run with elevated privileges unnecessarily.

scripts/apply-pairing-fix.sh:15

ORIGINAL_FILE="/usr/lib/node_modules/openclaw/dist/telegram/bot-message-context.js"
Remediation: 1. Check for required permissions before attempting modifications. 2. Provide clear warnings about privilege requirements. 3. Suggest alternative approaches that don't require system-level modifications. 4. Implement proper error handling for permission-denied scenarios. 5. Consider user-space alternatives to system package modification.
HIGH Unsafe Pattern Matching and Code Replacement Unauthorized Tool Usellm

The script uses simple sed pattern matching to modify JavaScript code without validating the surrounding context or ensuring the modification is safe. The pattern 'if (created) {' could potentially match unintended code locations, and the replacement doesn't verify that the modification maintains code integrity or doesn't introduce syntax errors.

scripts/apply-pairing-fix.sh:25

sed 's/if (created) {/if (code) {/' "$ORIGINAL_FILE" > "$ORIGINAL_FILE.tmp" && mv "$ORIGINAL_FILE.tmp" "$ORIGINAL_FILE"
Remediation: 1. Implement more robust pattern matching with context validation. 2. Verify the modification doesn't break JavaScript syntax. 3. Use AST-based code transformation instead of text replacement. 4. Add pre-flight checks to validate the target code structure. 5. Implement rollback mechanisms if modification fails. 6. Test the modified code before replacing the original.
MEDIUM Inadequate Error Handling and Recovery Resource Abusellm

The script uses 'set -e' to exit on errors but doesn't implement proper cleanup or rollback mechanisms. If the modification fails partway through, the system could be left in an inconsistent state with a partially modified file and no clear recovery path.

scripts/apply-pairing-fix.sh:6

set -e  # Exit on any error
... (no trap or cleanup handlers)
Remediation: 1. Implement trap handlers for cleanup on error/exit. 2. Add rollback functionality to restore from backup on failure. 3. Validate the modified file before replacing the original. 4. Provide clear error messages and recovery instructions. 5. Test modifications in a safe environment before applying to production files.
MEDIUM Misleading Skill Description and Scope Social Engineeringllm

The skill description presents this as a 'customization' or 'modification' feature, but it actually performs invasive system-level changes to installed software. The description doesn't adequately warn users about the risks of modifying system packages, potential warranty/support implications, or the fact that updates to OpenClaw will overwrite these changes.

SKILL.md

Description: Modify OpenClaw's Telegram pairing logic so unapproved users receive pairing codes on every /start message before approval.

The skill presents this as a routine customization without emphasizing the invasive nature of modifying system-installed packages.
Remediation: 1. Clearly label this as an 'advanced/dangerous' modification. 2. Warn about risks of modifying system packages. 3. Explain that updates will overwrite changes. 4. Recommend contacting OpenClaw developers for proper feature requests. 5. Suggest configuration-based alternatives if available. 6. Require explicit user acknowledgment of risks.
LOW Skill does not specify a license Policy Violationstatic

Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.

SKILL.md

Remediation: Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)
LOW Missing Metadata Fields Data Exfiltrationllm

The skill manifest is missing optional but recommended metadata fields: license, compatibility, and allowed-tools. While not a security threat, this reduces transparency about the skill's requirements and behavior.

SKILL.md

license: Not specified
compatibility: Not specified
allowed-tools: Not specified
Remediation: Add complete metadata to the YAML frontmatter: 1. Specify license (e.g., MIT, Apache-2.0). 2. Document compatibility requirements (requires OpenClaw installation, root/sudo access). 3. Declare allowed-tools: [Bash] to indicate shell script execution.

What is in the package

FileKindSize
SKILL.mddoc5.9 KB
scripts/apply-pairing-fix.shscript1.6 KB

Package contents recorded 2026-10-22. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.

What we checked

What we did not check

Sources

Related skills