Security audit

test-1-1

Security checks across malware telemetry and agentic risk

Overview

This is a WeChat Pay delegated-withholding documentation skill with financial integration examples, but it does not install executable code or directly perform payment actions.

Install only if you are working on WeChat Pay delegated-withholding integration. Treat all payment, refund, deduction, and termination examples as production-sensitive: use HTTPS callback URLs, verify signatures, confirm user/business authorization, test with safe amounts or sandbox-like flows where available, and keep API keys/certificates outside prompts and source code.

SkillSpector

By NVIDIA

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The example URL encodes a plaintext HTTP notify_url, which can lead integrators to deploy an insecure callback endpoint for payment-related contract notifications. Because these callbacks may carry sensitive business events and rely on integrity and authenticity checks, using HTTP exposes them to interception, tampering, downgrade, or misdelivery risks on untrusted networks.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: This document explains how to call a real WeChat Pay withholding API that can trigger actual user fund deductions, but it does not prominently warn operators that the action is financially sensitive and can move real money. In an agent skill context, this omission increases the chance that users or downstream automation treat the example as routine sample code and initiate unintended debits without adequate confirmation, sandbox guidance, or operational safeguards.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: This document describes an account/contract termination operation but does not clearly warn that the action is destructive, may affect future automatic deductions, and may require explicit business/user confirmation before execution. In an integration skill meant to guide developers, omission of such warnings can increase the likelihood of unsafe implementation or accidental cancellation flows.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical

Code: suspicious.exposed_secret_literal
Location: references/1-商户/接入指南/签名与验签规则.md:201

File appears to expose a hardcoded API secret or token.

Critical

Code: suspicious.exposed_secret_literal
Location: references/2-服务商/接入指南/签名与验签规则.md:197