solana@0.28.16
CAUTION· install onlyPublisher claims: "Loot boxes, gacha, shops, lotteries, auctions, NFT staking, crafting and rewards on Solana without writing a smart contract: one shared program, its JS client, a CLI, and an MCP server and skill so Claude Code, Codex or any AI agent can design, check, sim" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 78/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. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
const fromEnv = globalThis.process?.env?.XSOLANA_CLUSTER?.trim() || null;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.export function clusterRpcUrl(url = globalThis.process?.env?.XSOLANA_RPC_URL || null) {Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…a.com gives some), real SOL for one whose file says "network": "mainnet". Then: npx -y @xgamesfun/solana@${PACKAGE_VERSION} approve xsolana.json --keypair ${word}`, …Fix: Pin versions and sources; vendor anything fetched at install time./** This package's exact version: every command the tools hand a person names it, so npx runs this very release. */Fix: Pin versions and sources; vendor anything fetched at install time.return platform === 'win32' ? { command: 'cmd', args: ['/c', 'npx', ...npx] } : { command: 'npx', args: npx };Fix: Pin versions and sources; vendor anything fetched at install time.… loot economy (* = required):` : `A loot economy is one JSON spec (xsolana.json) on the shared loot program ${IDL.metadata.version}, on devnet or on mainnet (its "network"; devnet when it names none). Nobody writes a contract: the spec is …Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.const npx = ['-y', `--package=@xgamesfun/solana@${version}`, 'xsolana', 'mcp'];Fix: Pin versions and sources; vendor anything fetched at install time.* The command that starts the server: this checkout's (`local`), or the published package's. On Windows, npx is aFix: Pin versions and sources; vendor anything fetched at install time.…on the person’s own computer and is signed there by a key file. In that folder: npx -y @xgamesfun/solana@${PACKAGE_VERSION} keygen ~/.config/xsolana/<name>.json makes…Fix: Pin versions and sources; vendor anything fetched at install time.// opencode, Cline). It has no dependencies, so `npx -y --package=@xgamesfun/solana@<version> xsolana mcp` starts in theFix: Pin versions and sources; vendor anything fetched at install time.`${target} can be read by other users of this machine (its mode is ${(info.mode & 0o777).toString(8)}). Run: chmod 600 ${target}`,Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.text: `${name} works on the person’s own files, so it runs only in the local server (npx -y --package=@xgamesfun/solana@${PACKAGE_VERSION} xsolana mcp).`,Fix: Pin versions and sources; vendor anything fetched at install time.export const keygenCommand = keyFile => `npx -y @xgamesfun/solana@${PACKAGE_VERSION} keygen ${keyFile}`;Fix: Pin versions and sources; vendor anything fetched at install time.…son what a cheater gets).', `To go live, the spec goes in a file named xsolana.json on the person’s own computer and is signed there by a key file. In that folder: npx -y @xgamesfun/solana@${PACKAGE_VERSION} keygen ~/.config/xsolana/<name>…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…s (every step, in order, and its cost) and the commands that do it (each starts npx -y @xgamesfun/solana@${PACKAGE_VERSION} for this exact version: give them as they …Fix: Pin versions and sources; vendor anything fetched at install time.return `npx -y @xgamesfun/solana@${PACKAGE_VERSION} approve${name ? ` ${name}` : ''}`;Fix: Pin versions and sources; vendor anything fetched at install time.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
No advisories in OSV for @xgamesfun/solana@0.28.16 as of 2d ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim xgamesfun: 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.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- 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.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.