stellar-agentic-wallet@1.8.8
CAUTION· static onlyPublisher claims: "A Stellar USDC wallet skill for AI agents. Pay for 402-gated APIs via MPP Router or x402 facilitators, check balances, manage USDC trustlines, swap XLM→USDC on the Classic DEX, pay a Stellar deposit address directly with a memo, and bridge/send USDC cross-chain to Ethereum, Arbitrum, Base, BSC, Polygon, Solana, or back to Stellar via Rozo. Client-only, sponsored mode, testnet and mainnet. Triggers on "stellar wallet", "pay per call stellar", "x402 stellar", "mpprouter", "check stellar balance", "swap xlm to usdc", "add usdc trustline", "bridge from stellar", "send usdc cross-chain", "pay this deposit address with memo", "fund this invoice on stellar", "pay for api with stellar", or when the user shares a G... address with a payment intent." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 55/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…than the working-directory default, the path it came from is printed first. **`.env` files are read only from a directory you name.** They are your files and routi…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."# Stellar wallet secret — DO NOT COMMIT. chmod 600.\n" +Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.* decide whether it may look at .env files next to the secret file: namingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Pass on the command line (no env vars, no .env files):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.6. Only when you named a path with `--secret-file`: `STELLAR_SECRET` (or legacy aliases) in `.env.prod` then `.env` in that directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.path.join(path.dirname(secretSource.path), ".env.prod"),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…ewrite or remove a key file on your behalf. **Keep main-wallet secrets out of `.env` files in this directory.** The fallback exists for legacy compatibility; prefe…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (pat.startsWith(".env") && base.startsWith(".env")) return true;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(default `.stellar-secret`), falling back to `.env.prod` then `.env` onlyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- 🔐 **Never commit `.stellar-secret`, `.env`, `.env.prod`, or `.secrets/*`.**Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* to STELLAR_SECRET in .env.prod then .env (same directory).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Simple glob: "*.env" styleFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.🔐 Never commit .stellar-secret, .env, .env.prod, or .secrets/*.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.path.join(path.dirname(secretSource.path), ".env"),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `~/.env` or any other file belonging to the user is not, and never appearsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…ecret never has to exist as a plaintext file in your working directory or in a `.env` alongside your other configuration. The identity path prints no warning. Be c…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* Fallback: if the secret file does not exist, checks .env.prod then .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log("(delegating to send-payment)");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.**Never paste your secret into any UI or chat you do not fully control.** Keep it in the secret file only.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.console.log("Sending Stellar USDC to deposit address...");Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(` Send: ${xlmAmount} XLM`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`Poll status: ./node_modules/.bin/tsx skills/send-payment/status.ts ${intent.id}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(` You will send: ${totalSource} USDC on Stellar`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
25 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim shawnmuggle: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Prompting user to enter sensitive credentials≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.