Back to skill

Security audit

Github To Skill

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only guide for converting GitHub projects into OpenClaw skills, with no executable code or hidden runtime behavior found.

This skill is low risk as installed because it is only a reference document. Users should still review any third-party GitHub project they convert, avoid packaging secrets such as .env files or keys, and verify licenses and dependencies before creating a real skill from external code.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (6)

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 · README.md (reported line 66)May include surrounding context.

md
| 文件 / File | 原因 / Reason |
|------------|--------------|
| .env | 可能含 API Key / May contain API keys |
| *.key, *.pem | 密钥文件 / Key files |
| credentials | 凭据 / Credentials |

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 · SKILL.md (reported line 76)May include surrounding context.

md
| 文件 / File | 原因 / Reason |
|------------|--------------|
| .env | 可能含 API Key / May contain API keys |
| *.key, *.pem | 密钥文件 / Key files |
| credentials | 凭据 / Credentials |

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 · SKILL.md (reported line 140)May include surrounding context.

md
| 文件 / File | 原因 / Reason |
|------------|--------------|
| .env | 可能含 API Key / May contain API keys |
| *.key, *.pem | 密钥文件 / Key files |
| credentials | 凭据 / Credentials |

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The description string is entirely in Chinese and presents the skill as a reference guide without indicating that language selection is optional. Under the policy, forcing a specific language or locale without user opt-in is a natural-language policy violation unless clearly justified as region-specific.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
27% confidence
Finding

The document is presented bilingually in Chinese and English, but it does not explicitly impose a single mandatory language for user interaction. Because it already includes English and does not clearly require one locale, this is at most a weak potential policy concern rather than a clear violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The document title and primary presentation are in Chinese, with English provided secondarily, but there is no statement that users may choose their preferred language or locale. The policy requires avoiding forced language constraints unless the locale limitation is explicitly justified or optional.

Content

No source excerpt is available for this finding.