Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md ### 调用流程(scripts/paid-call.mjs)
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly transparent about paid parenting advice, but its payment workflow has review-worthy problems including an unrelated payment intent label and an unpinned external installer.
Review before installing. Only use this if you are comfortable sending parenting prompts to the disclosed remote service and paying through Alipay. Avoid running the unpinned @latest installer unless you can verify the package version and publisher, and treat the unrelated payment description as a reason to confirm charges carefully before approving payment.
Referenced artifact was not completely inspected
### 调用流程(scripts/paid-call.mjs)
Referenced artifact was not completely inspected
### 调用流程(scripts/paid-call.mjs)
Referenced artifact was not completely inspected
### 调用流程(scripts/paid-call.mjs)
Referenced artifact was not completely inspected
### 调用流程(scripts/paid-call.mjs)
Referenced artifact was not completely inspected
### 调用流程(scripts/paid-call.mjs)
The file's behavior is a paid remote invocation and payment orchestration flow, not parenting or early-education assistance logic. This mismatch is dangerous because it obscures the true capabilities of the skill, making trust decisions harder and increasing the risk that users authorize networked payment operations they did not expect from the declared skill purpose.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill is presented entirely in Chinese, beginning with the display name and continuing through the instructions, with no indication that users may choose another language. Under the policy, forcing a specific language without opt-in or a clearly justified region-specific limitation is a natural-language policy concern.
The trigger list contains broad everyday parenting phrases such as 育儿, 早教, 几岁会, and 亲子游戏, which can match normal conversation too aggressively and cause unintended invocation. In practice this can route unrelated or sensitive family discussions into a paid external workflow, increasing privacy and billing risk.
The skill instructs users to run npx -y @alipay/agent-payment@latest install, which fetches and executes the latest package version at install time. This creates a supply-chain risk: if the package is compromised or a breaking/malicious version is published, users may execute unreviewed code on their systems.
This code file contains natural-language documentation and runtime messages entirely in Chinese, including required usage guidance and error/help text. That effectively imposes a specific language on users without any opt-in or alternative, which matches the locale-policy violation criteria.
The script instructs users to install and run '@alipay/agent-payment@latest' via npx without pinning a specific version. This creates a supply-chain risk: a compromised or malicious future package release could be fetched and executed automatically on the user's machine with the script's trust context.
The script launches external programs ('curl' and 'alipay-bot') even though such behavior is not justified by the stated parenting-assistant functionality. Spawning subprocesses broadens the attack surface through PATH hijacking, unsafe environment inheritance, and hidden network/payment side effects that users would not reasonably expect in this context.
The payment intent summary references '种草图文笔记创作', which is unrelated to parenting or early education. This inconsistency is a strong indicator of copied or repurposed payment code and can mislead users during authorization, increasing the risk of deceptive consent or mis-billing.
The runtime error message again directs users to execute an unpinned '@latest' package install command. Repeating this guidance increases the chance that users will fetch whatever version is currently published, exposing them to remote code execution through package compromise or typosquatting-like publisher takeover scenarios.
No suspicious patterns detected.