Back to skill

Security audit

morning-brief

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Chinese holiday countdown reminder with limited network access and local caching, though its dependency pinning could be improved.

Before installing, consider that the skill runs automatically every morning, contacts an external holiday-calendar endpoint, and caches the response locally. For stronger supply-chain safety, use a lockfile or pinned dependency versions.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
package.json:19
Finding

Unpinned Dependencies and Missing Lockfile Permit Unreviewed Package Code

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (8)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The README presents the skill entirely in Chinese and the sample output is also fixed to Chinese, but it does not say the skill is China-specific or that users can choose their preferred language. This can violate language/locale policy when a skill implicitly forces one language without opt-in or documented regional justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The manifest description is written only in Chinese and describes the skill as a Chinese holiday countdown/reminder, which implies a fixed language/locale experience without any user opt-in or language choice. Under the policy, locale or language constraints should be optional or clearly justified as region-specific.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The script emits its user-facing text entirely in Chinese and does not provide any option to choose another language or locale. Under the policy, forcing a specific language without opt-in is a natural-language policy violation unless the locale restriction is explicitly documented and justified.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

This code retrieves holiday data from an external URL and writes it to a local JSON cache file, but there is no user-facing notice before or during these operations. While the script logs the final output and reports errors, it does not disclose that it performs network access and persistent local file writes.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
93% confidence
Finding

The manifest description is written as a Chinese-only user-facing skill description, indicating the skill provides content in a specific language. There is no accompanying indication that users can choose another language or opt in to the locale, which can violate language/locale policy requirements.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
90% confidence
Finding

Using a caret range for axios allows installation of newer matching versions without strict review, which weakens build reproducibility and can unexpectedly pull in vulnerable or behavior-changing releases. Because axios is a network-facing library with multiple advisories, loose versioning increases supply-chain and exposure risk.

Content

Scanner excerpt · package.json (reported line 20)May include surrounding context.

json
"author": "OpenClaw Community",
  "license": "MIT",
  "dependencies": {
    "axios": "^1.6.0",
    "dayjs": "^1.11.0"
  }
}

Unverifiable Dependency: axios has 16 known advisory(ies) (CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more), but the manifest does not pin a version, so it is unknown whether the installed release is affected

Low
Category
Supply Chain
Confidence
88% confidence
Finding

The manifest references axios without an exact pinned version, and axios has multiple known advisories in some releases. Without a lockfile or exact version, it is not possible to verify whether deployments will resolve to a safe release, leaving the skill potentially exposed to known issues such as SSRF or request-handling weaknesses depending on usage in code.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
82% confidence
Finding

Using a caret range for dayjs permits automatic minor/patch upgrades, reducing reproducibility and increasing supply-chain uncertainty. While the direct risk is lower than for a network client, unpinned dependencies still make it harder to guarantee the deployed code matches what was reviewed.

Content

Scanner excerpt · package.json (reported line 21)May include surrounding context.

json
"license": "MIT",
  "dependencies": {
    "axios": "^1.6.0",
    "dayjs": "^1.11.0"
  }
}