ceaser-send@1.3.0
CAUTION· static onlyPublisher claims: "Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operat..." 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-18 and scored it 63/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. 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
- The pending-tx.json file is created with 0600 permissions and deleted after successful sendFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.npx -y ceaser-mcp <subcommand> [args]Fix: Pin versions and sources; vendor anything fetched at install time.…p/notes.json.tmp && mv ~/.ceaser-mcp/notes.json.tmp ~/.ceaser-mcp/notes.json && chmod 600 ~/.ceaser-mcp/notes.json ``` **IMPORTANT:** Always restore file permissions…Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…ommand automatically saves the unsigned transaction to `~/.ceaser-mcp/pending-tx.json`. The sign-and-send helper auto-detects this file, so you do NOT need to pass the transaction data …Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.notes: 'Auto-detects ~/.ceaser-mcp/pending-tx.json if no args given. File is deleted after successful send.',Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- **File permissions:** After ANY modification to notes.json, run `chmod 600 ~/.ceaser-mcp/notes.json`.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.npx -y ceaser-mcp shield USER_AMOUNTFix: Pin versions and sources; vendor anything fetched at install time.The helper automatically reads the unsigned TX from `~/.ceaser-mcp/pending-tx.json` and deletes the file after a successful send.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…cp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between …Fix: Pin versions and sources; vendor anything fetched at install time.npx -y ceaser-mcp notesFix: Pin versions and sources; vendor anything fetched at install time.npx -y ceaser-mcp import "$UPDATED_BACKUP"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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zyra-v21: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.