Back to skill

Security audit

qywx-notify

Security checks for vulnerabilities and agentic risk

Overview

This skill does what it claims, but it can expose sensitive webhook credentials and can be pointed at arbitrary URLs from the host running it.

Review before installing. Use only in a trusted, single-user context unless the webhook handling is fixed. Do not put real WeCom webhook URLs into this version if logs or command outputs are visible to others, and restrict or remove caller-supplied webhook URLs so the skill cannot be used as a general network request proxy. Pin dependencies and rotate any webhook that may already have appeared in logs.

Vulnerability Patterns
  • 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
  • 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 (2)

T09 · Insecure Skill Coding Practices

Warning
Location
index.js:43
Finding

Webhook credentials are exposed through logs and returned objects

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
index.js:213
Finding

Unrestricted webhook URLs enable server-side request forgery

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (6)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The primary purpose matches the description: this is a WeChat Work/WeCom notification sender. However, the declared permissions are empty, while the code performs outbound HTTP POST requests to provided or configured webhook URLs using axios. That network capability is material and should be declared. In addition, the skill exposes extra operational capabilities beyond simple notification sending: a test command that sends a live test notification and a config command that returns configuration details. These are related to the skill but are not reflected in the description. No evidence of unrelated data exfiltration or a materially different purpose was found.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
99% confidence
Finding

Initialization logging serializes and prints the entire runtime configuration, which includes the defaultWebhook secret. Logs are commonly accessible to operators, support tooling, or aggregated log platforms, so this creates a durable secret leak that can enable unauthorized message sending if the webhook is recovered.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill logs the full default webhook URL without warning or redaction, exposing a credential-like secret in plaintext. In the context of a notification skill, the webhook is the primary authorization mechanism, so leaking it directly undermines access control to the downstream WeCom group bot.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The config command returns the full this.config object, which includes defaultWebhook in plaintext. A WeCom webhook URL is effectively a secret because anyone who obtains it can send arbitrary messages to the target group, so exposing it through an operational command is an unnecessary secret-disclosure path for this skill.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The dependency is specified with a caret range (^1.6.0), which allows different installed versions over time instead of a fully fixed release. This weakens supply-chain reproducibility and can silently introduce vulnerable or behavior-changing versions during installation, especially in a notification skill that makes outbound network requests.

Content

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

json
}
  },
  "dependencies": {
    "axios": "^1.6.0"
  },
  "engines": {
    "node": ">=16.0.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
78% confidence
Finding

The manifest depends on axios without an exact pinned version, and axios has a history of advisories including SSRF- and proxy-related issues. Because this skill sends notifications via outbound HTTP requests, any affected axios release could be security-relevant in this context, and the non-pinned range makes it impossible to verify from the manifest alone whether deployments are safe.

Content

No source excerpt is available for this finding.