Back to skill

Security audit

ERPNext

Security checks for vulnerabilities and agentic risk

Overview

ERPNext changes require user confirmation, but the automatic remote-software installation workflow needs review.

Review and explicitly approve the CLI installation before allowing setup. Prefer a verified, version-pinned release and check whether it installs skills into other agents. Use narrowly scoped ERPNext credentials, consider OOMOL's access to business data, and retain write/delete confirmations. The downloaded installers and hosted runtime were not independently verified.

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
  • 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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The supplied code installs software from an external service rather than performing the declared ERPNext data operations. Nothing in the chunk establishes this installation as a supporting ERPNext dependency. The remote script's contents are not supplied, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a mutable HTTPS response directly into bash executes remote code with the invoking user's permissions, without a pinned version or independently checked integrity. Compromise of the installer distribution path could therefore expose local files and credentials or install persistent malware; the PowerShell alternative has the same underlying risk. The documented dependency and conditional fallback explain the intended use but do not remove this supply-chain exposure.

Content

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

The setup workflow executes remotely downloaded installation scripts without a system-integrity warning.

Medium
Category
Output Handling
Confidence
95% confidence
Finding

The fallback setup instructs the agent to execute downloaded shell or PowerShell code without explaining that installation can modify the local system or requiring explicit user approval. Restricting setup to a missing-CLI error reduces exposure, but an ERPNext request alone does not clearly authorize arbitrary local installer execution.

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 84)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.

## Resources