Security audit

Orderly Sdk Dex Architecture

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only skill for building an Orderly Network DEX, and the scanned concerns are explained by normal example project configuration rather than hidden or unsafe behavior.

Before using this skill, review the generated DEX configuration carefully, especially broker ID, mainnet versus testnet defaults, wallet connector behavior, and any manually downloaded TradingView files or npm packages. Nothing in the artifact suggests hidden execution or credential theft, but financial applications should be configured deliberately before production use.

A.I.G

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

SkillSpector

Vulnerability Patterns

Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
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

Findings (2)

Credential Access

High

Category: Privilege Escalation
Content: │ │ └── storage.ts # Local storage utils │ └── styles/ │ └── index.css # Global styles + Tailwind ├── .env # Build-time env vars ├── index.html ├── package.json ├── tailwind.config.ts
Confidence: 60% confidence
Finding: Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Natural-Language Policy Violations

Medium

Confidence: 96% confidence
Finding: The example config hard-codes `locale="en"` in `LocaleProvider`, which imposes a specific language by default in the skill guidance. The policy allows locale constraints only when the user is given a choice or the restriction is clearly documented and justified, neither of which is present here.

Static analysis

No suspicious patterns detected.