ziniao-erp-api-doc

• Outcome: Pass
• Latest audit: Sep 15, 2026 · 1:35 AM UTC
• Version: 1.0.0

Overview

This is a documentation-only ERP API reference skill with high-impact administrative and billing endpoints clearly in scope, but it does not install code, run commands, persist state, or hide behavior.

Install only if you need Ziniaoniao ERP API documentation. Treat any real API Key, employee passwords, proxy credentials, mobile numbers, account IDs, and company data as sensitive; do not paste secrets into shared chats or logs. Before using the documented endpoints, require explicit user approval for deletions, authorization changes, role changes, account cache clearing, device binding/unbinding, purchases, renewals, and enabling auto-renewal.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (17)

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 90% confidence

Finding

This markdown file documents deletion, enable/disable, member/account reassignment, and account policy add/remove endpoints, but it does not include any caution that these actions can immediately change user access or remove existing policy bindings. For markdown files, missing warnings about behaviors that can affect user data or system integrity should be flagged when the description omits user-facing disclosure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

This markdown file describes deletion endpoints for webpages but does not include any warning that the operation removes configured data or may be irreversible. For markdown files, SQP-2 applies when descriptions omit warnings about behaviors that could affect user data or system integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 88% confidence

Finding

The file documents a group deletion API but provides no caution about deleting organizational configuration data or potential downstream effects on grouped webpages. Under SQP-2 for markdown files, potentially destructive behavior should be accompanied by a user-facing warning.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 90% confidence

Finding

This markdown file documents an endpoint that clears all authorization relationships for specified accounts, which can materially affect access control and user operations. While L54 describes what the endpoint does, it does not provide any warning, confirmation guidance, or caution about the destructive impact of removing all authorizations.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 88% confidence

Finding

This markdown file documents an account deletion API but does not include any warning that the operation removes accounts or that callers should confirm intent before use. Under the markdown-specific warning criterion, destructive behavior affecting user data/system state should be disclosed clearly in the skill description.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 86% confidence

Finding

The document describes an endpoint that clears account cache, including an option to clear all, but provides no warning about possible logout, loss of session state, or other user-impacting effects. Markdown documentation should warn users when behavior can affect data, privacy, or system integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 94% confidence

Finding

The document exposes destructive bulk operations such as replace, remove, clear, delete, and unbind, and explains their semantics, but it does not prominently warn that some actions can overwrite all existing tags or remove all tags from multiple accounts. In an API-integration skill, this omission can lead an agent or developer to invoke high-impact endpoints without adequate confirmation or safeguards, causing accidental large-scale data modification.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

This is a markdown file, so SQP-2 applies to missing warnings in documentation. The guide instructs users to retrieve and send an API Key as a Bearer token, but it does not warn users to keep the key secret, avoid committing it to source control, or avoid exposing it in logs and shared examples.

Content

No source excerpt is available for this finding.

External Transmission

Medium

• Category: Data Exfiltration
• Confidence: 60% confidence

Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · reference/api-guide.md (reported line 94)May include surrounding context.

JavaScript（Fetch）

javascript

fetch("https://sbappstoreapi.ziniao.com/openapi-router/superbrowser/rest/v1/erp/store/list", {
  method: "POST",
  headers: { "Authorization": "Bearer 你的API_Key", "Content-Type": "application/json" },
  body: JSON.stringify({ companyId: 123456 }),

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 92% confidence

Finding

This markdown file describes department deletion and later employee status changes including disable/delete, but it provides no warning that these actions can affect user data or access. Under the markdown-specific SQP-2 criteria, descriptions of behaviours that may impact system integrity or user accounts should disclose that risk.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 87% confidence

Finding

The file documents employee creation with sensitive fields such as password, mobile number, and login-control settings, but does not include any warning about handling credentials and personal data carefully. For markdown files, omission of warnings around privacy- or security-impacting behaviour is in scope for SQP-2.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 95% confidence

Finding

The purchase and renewal APIs perform billable actions and the documentation only briefly notes that balance is required, without prominently warning that calls may spend funds or create orders. In an agent-integrated environment, this omission is dangerous because a model or operator may treat these endpoints as informational and unintentionally incur charges.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 94% confidence

Finding

The auto-renewal toggle controls recurring billing behavior but the documentation does not warn about ongoing financial impact when enabling it. In a skill used for integration planning or agentic API usage, lack of such warning raises the risk of silently turning on recurring charges that persist beyond a single action.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 90% confidence

Finding

The binding and unbinding endpoints can change account-to-device associations and explicitly include a defyWarning option that defaults to ignoring risk warnings. In an agent skill context, documenting these operations without strong user-facing cautions increases the chance that an automation triggers disruptive account reassignment or bypasses safety checks without informed confirmation.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 90% confidence

Finding

The self-managed device add/edit APIs accept sensitive connection credentials such as proxy usernames and passwords, yet the documentation provides no warning about secure handling, storage, masking, or logging risks. In an agent setting, these fields may be echoed in prompts, logs, traces, or analytics, leading to credential exposure and downstream compromise of proxy or device infrastructure.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 86% confidence

Finding

This markdown file documents actions that add roles and modify permissions, which can materially affect system access and user privileges. The descriptions list parameters and responses only, with no warning that these operations change authorization state or should be used cautiously by authorized operators.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 89% confidence

Finding

The 'ERP-调整角色' section describes changing roles for a list of users, which directly alters those users' access rights. The markdown provides no warning about the security impact, audit expectations, or need for careful confirmation before applying changes.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.