T01 · Skill Instruction Hijacking
- Location
SKILL.md:113- Finding
Skill instructions override the Agent role and require verbatim forwarding of untrusted output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent cloud-backed dating matcher, but it needs Review because its photo, credential, environment, and scheduling behavior are broader than users would reasonably expect.
Install only after reviewing the publisher and preferably in an isolated OpenClaw workspace with a dedicated LOVECLAW_API_TOKEN. Do not place unrelated API_TOKEN secrets in the shared workspace .env, verify LOVECLAW_API_BASE before use, avoid submitting local file paths as photos, and require fixes for photo path validation, session-file permissions, global session-registry access, and dependency updates before using it with real users.
SKILL.md:113Skill instructions override the Agent role and require verbatim forwarding of untrusted output
scripts/cloud-handler.js:603User-controlled absolute paths can cause arbitrary readable local files to be uploaded
scripts/load-workspace-env.js:19A generic workspace API token can be loaded and transmitted as the LoveClaw bearer credential
scripts/cloud-data.js:7Unrestricted API-base configuration can redirect bearer credentials and sensitive user data
scripts/cloud-cron.js:27The reporting task reads the main Agent's global session registry
scripts/cloud-handler.js:230Sensitive registration state is persisted in plaintext without restrictive file permissions
protobufjs 7.5.4 is present as a transitive dependency of @grpc/proto-loader, and the advisories include denial-of-service and code-generation/injection issues. Even if only used transitively, protobuf parsers are often fed remote data, so malformed protobuf content could plausibly trigger crashes or unsafe behavior in services using Firebase/gRPC-related features.
protobufjs 8.0.0 is directly present and the advisory set includes parsing and code-generation issues that can lead to denial of service or unsafe generated behavior. Because protobuf-related libraries often handle structured remote input, this is a substantive supply-chain risk rather than a false positive.
protobufjs 4.1.3 is an old transitive dependency under tablestore and inherits the same family of protobuf parsing/codegen issues. Its age and multiple critical advisories increase concern, especially for a skill storing user-related records where structured remote data may be processed server-side or through SDKs.
protobufjs 8.0.0 is explicitly flagged with multiple critical advisories including denial-of-service and code-generation/injection issues. Because this skill description references cloud-side processing and report generation, any use of protobufjs for parsing or generating structured data from external or service-supplied input could let an attacker crash processing or potentially exploit unsafe code-generation paths, making the dependency especially risky in a backend-integrated skill.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
If the skill locally formats reports and handles partner PII such as name, city, and phone, then it is doing more than simple notification routing and increases the amount of sensitive data exposed in the agent runtime. That widens the blast radius of compromise, logging mistakes, or prompt/output leakage.
Referenced artifact was not completely inspected
handler: ./scripts/cloud-handler.js
Referenced artifact was not completely inspected
handler: ./scripts/cloud-handler.js
Referenced artifact was not completely inspected
handler: ./scripts/cloud-handler.js
Referenced artifact was not completely inspected
- **联网**:`scripts/cloud-data.js` 向云函数 HTTPS 端点发请求(默认 URL 见源码,可用 `LOVECLAW_API_BASE` 覆盖)。
Referenced artifact was not completely inspected
- **联网**:`scripts/cloud-data.js` 向云函数 HTTPS 端点发请求(默认 URL 见源码,可用 `LOVECLAW_API_BASE` 覆盖)。
Referenced artifact was not completely inspected
| `scripts/cloud-cron.js` | 触发 FC 端匹配 `match`;遍历本机用户逐个获取报告 `report`。 |
The lockfile pins @grpc/grpc-js 1.9.15, and the cited advisories indicate malformed gRPC traffic can crash client/server processes. In this file the package is only a transitive dependency via Firebase/Firestore, so exploitability depends on whether the skill actually exposes or consumes gRPC paths, but it is still a real vulnerable dependency present in the shipped dependency graph.
brace-expansion 1.1.12 is present with multiple DoS-style expansion flaws. In a lockfile this is a real vulnerable package, but practical risk is lower unless the application feeds attacker-controlled glob or brace patterns into code paths using this library.
Detected: suspicious.dangerous_exec, suspicious.env_credential_access