Security audit

EntradeX

Security checks for vulnerabilities and agentic risk

Overview

This skill is transparent about DNSE trading, but it needs review because it can place real trades and installs an unpinned global npm package.

Review carefully before installing. Prefer an audited, pinned entradex-cli version in an isolated environment, use a limited DNSE account or narrowly scoped credentials, avoid storing secrets unless needed, and require explicit confirmation before any place, modify, or cancel trade command.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
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

Findings (1)

T08 · Insecure Dependencies

Error

Location: SKILL.md:13
Finding: Unpinned Global Installation of a Third-Party npm Package
Content: View full analysis
Remediation: View remediation
``` 2. Record and verify the expected npm artifact integrity hash and package provenance before installation. 3. Use a lockfile or an equivalent immutable dependency manifest where the execution environment supports it. 4. Prefer a project-local installation in an isolated, least-privileged environment instead of a global installation. 5. Disable npm lifecycle scripts during installation where compatible: ```bash npm install --ignore-scripts --save-exact entradex-cli@ ``` 6. Audit the package contents, transitive dependencies, lifecycle scripts, maintainer history, and repository-to-package correspondence for the exact pinned version. 7. Run the CLI under a dedicated low-privilege account or sandbox with access only to the files and network destinations required for DNSE operations. 8. Supply narrowly scoped trading credentials and rotate them immediately if package compromise or unauthorized access is suspected. 9. Vendor the reviewed source or include an auditable implementation in the project when stronger supply-chain assurance is required. ]]>

SkillSpector

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Static analysis

No suspicious patterns detected.