Back to skill

Security audit

Kingdee

Security checks for vulnerabilities and agentic risk

Overview

The Kingdee workflow has clear approval controls, but its automatic installation fallback and under-disclosed changes to other agents’ skills warrant review.

Review and approve CLI installation separately, using a reviewed, pinned release with integrity verification. Review its automatic skill synchronization before first use. OOMOL mediates enterprise requests and connection credentials, so use an appropriately limited Kingdee account and approve exact write targets. Restore the missing API index before relying on object-discovery workflows. The installer and connector runtime were not validated by this artifact review.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
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
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
93% confidence
Finding

The supplied chunk performs remote installer execution rather than any demonstrated Kingdee operation. Although dependency installation can be a supporting implementation detail, the provided content establishes no relationship between this Oomol installer and the declared Kingdee functionality. This assessment does not assume the unseen installer is malicious.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The command pipes a mutable remote script directly into Bash without verifying its integrity or reviewing its contents; the PowerShell alternative has the same weakness. Compromise of the installer distribution channel could execute arbitrary code with the agent's local privileges, potentially exposing accessible files and credentials despite server-side handling of Kingdee tokens.

Content

Scanner excerpt · SKILL.md (reported line 115)May include surrounding context.

Fallback setup executes remote installation scripts without warning the user about remote code execution or local system changes.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback instructs the agent to execute an installer when the CLI is missing without first explaining local changes or obtaining installation-specific approval. Authorization to perform a Kingdee task does not necessarily authorize installing software, and the write-confirmation rules address Kingdee state rather than local installation.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 136)May include surrounding context.

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

- **Ambiguous HTTP 401/403 or business error** — preserve the upstream error as reported; do not conclude that the application secret expired unless the response contains a documented credential signal.
- **Official operation documentation unavailable** — report the missing contract. Do not guess fields, enumerate documentation IDs, or fetch every operation.

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 · references/proxy-reference.md (reported line 16)May include surrounding context.

md
| Response fields | `/apiinfoparam/apiinfo/{apiInfoId}/paramfield/res` | Interpret an unfamiliar result                                           |
| Examples        | `/apiinfoparam/apiinfo/{apiInfoId}/paramjson`      | Inspect request/response shapes when needed                              |

These are documentation endpoints, not enterprise execution endpoints. Read them with a public HTTP tool or curl without Cookie, Authorization or application credentials. Check both HTTP status and the JSON `result` flag. Fields are in `dataList`; examples are in `data.requestJson` and `data.responseJson` and may themselves be JSON strings.

Walk parameter-tree `children` recursively, keeping full paths and case. Interpret `isMust`, `fieldType`, `defaultValue` and `description` together: conditional requirements and example strings such as `"false"` are not unconditional defaults. An empty response-field tree does not prove an empty business response; consult the example.