ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Elsa x402 API

v1.0.0

DeFi tools for portfolio analysis, token search, and swap execution via Elsa API with x402 micropayments

⭐ 0· 350·0 current·0 all-time
byJ Kishore Kumar@justjkk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
✓
Purpose & Capability
The skill's name/description (Elsa x402 DeFi API + micropayments) match what the code requests and does: it uses PAYMENT_PRIVATE_KEY to create a wallet client and attach x402 payment headers, calls Elsa endpoints, and optionally signs on-chain transactions using a trade key. The required secret is proportionate to the stated payment & signing features.
ℹ
Instruction Scope
SKILL.md instructs the agent and user to run the included TS scripts (npx tsx scripts/index.ts ...) and to set PAYMENT_PRIVATE_KEY (and optionally TRADE_PRIVATE_KEY). The instructions do not attempt to read unrelated system files or unrelated credentials, and they enforce dry-run/confirmation and budget checks. However the guidance explicitly tells users to put a private key into ~/.openclaw/openclaw.json (persistent file), which increases risk if the repo is untrusted or the file is not protected.
✓
Install Mechanism
There is no external download/install spec; the package contains a standard package.json/package-lock.json and depends on public npm packages (axios, viem, x402-axios, etc). No unusual or remote ad-hoc URL downloads or extract-from-arbitrary-URL steps are declared.
!
Credentials
Only PAYMENT_PRIVATE_KEY is declared as required (with TRADE_PRIVATE_KEY optional), which is expected for x402 payments and local signing. That said, a single required env that is a raw private key is highly sensitive: the skill expects you to store a hex private key in config and will use it to sign payment messages (and may be used for signing if TRADE_PRIVATE_KEY is not set). This is proportionate for the feature set but high-risk in practice — it must be handled with strict operational controls (dedicated low-value payment wallet, protect config file, prefer ephemeral or hardware-backed signing if possible).
✓
Persistence & Privilege
The skill does not request always:true and does not claim to modify other skill configurations. It asks the user to add env into OpenClaw config for the skill to run (normal). Execution tools are opt-in (ELSA_ENABLE_EXECUTION_TOOLS) and SKILL.md enforces dry-run/confirmation rules.
What to consider before installing
This skill appears to implement what it claims (pay-per-call x402 payments + Elsa API access), but it requires you to provide a raw private key (PAYMENT_PRIVATE_KEY) that the code will use to sign payment messages and (if execution enabled) may sign transactions. Before installing: - Only use a dedicated payment wallet seeded with a small USDC balance (minimal funds). Do not put funds you cannot afford to lose into the PAYMENT_PRIVATE_KEY wallet. Consider using a separate TRADE_PRIVATE_KEY wallet for actual swaps. - Avoid storing high-value private keys in plaintext files. If you must place the key in ~/.openclaw/openclaw.json, ensure that file is permission-restricted, encrypted, or managed via a secure secret store. Prefer hardware-backed signing or ephemeral keys if supported. - Verify provenance: the registry metadata lists no homepage and the source is unknown. Inspect the repository (github.com/HeyElsa/elsa-openclaw referenced in docs) and vet the x402-axios dependency and other npm packages for supply-chain risk before running npm install. - Review the included code (especially scripts/x402Client.ts, scripts/index.ts, and utilities that write logs) to ensure audit logs and any local files are written to safe locations (ELSA_AUDIT_LOG_PATH) and that no unexpected remote endpoints are contacted beyond the documented Elsa API endpoints (x402.heyelsa.ai / x402-api.heyelsa.ai). - When enabling execution (ELSA_ENABLE_EXECUTION_TOOLS=true), require an explicit human verification step and confirm the confirmation token logic is enforced in your deployment. Because the skill asks for a very sensitive secret and the registry entry lacks clear provenance, treat it as suspicious until you confirm the code and origin and apply operational protections.

Like a lobster shell, security has layers — review code before you run it.

latestvk972e5jqs0k0x1ha0n4g92826181z901

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

EnvPAYMENT_PRIVATE_KEY
Primary envPAYMENT_PRIVATE_KEY

Comments